steve0603

讨论了EMIR 1.2版本在UAT环境的准备工作,包括角色映射更新、用户验证流程及产品增强请求的时间安排。

0|||8|||SS will be late, traffic jam|||2015-06-04 17:44:04|||0:0:0:0:0:0:0:1
8|||14|||get started|||2015-06-04 17:44:22|||0:0:0:0:0:0:0:1
14|||22|||anything to talk about before going through agenda? |||2015-06-04 17:44:47|||0:0:0:0:0:0:0:1
22|||31|||agenda has been sent out just now|||2015-06-04 17:45:10|||0:0:0:0:0:0:0:1
31|||52|||1. EMIR, prod release for 1.2 , everything in UAT, Steve haven't get a chance to check|||2015-06-04 17:46:50|||0:0:0:0:0:0:0:1
52|||75|||so ?? the devmon auth, make sure we create /add role ?? for UK ?? fcm tech users. |||2015-06-04 17:49:20|||0:0:0:0:0:0:0:1
75|||103|||yes, acutally, in our db, we just need to update all of the userid from old to new. keep the same role and permission. |||2015-06-04 17:51:00|||0:0:0:0:0:0:0:1
103|||113|||Steve not sure update will work, because most of the user have the login in prod???|||2015-06-04 17:52:06|||0:0:0:0:0:0:0:1
113|||117|||user id has to be unique|||2015-06-04 17:52:55|||0:0:0:0:0:0:0:1
117|||123|||share copy?? id share between cc and regconn now.|||2015-06-04 17:53:30|||0:0:0:0:0:0:0:1
123|||132|||because CFD?? is part of the release, but it should be??|||2015-06-04 17:54:45|||0:0:0:0:0:0:0:1
132|||144|||so , I think it's better if we add the role to the existing cc user. |||2015-06-04 17:57:00|||0:0:0:0:0:0:0:1
144|||151|||is ?? everyone would have the request certificate for production|||2015-06-04 18:00:31|||0:0:0:0:0:0:0:1
151|||164|||so they all have an existing id, so we can just rename the EMIR/previous id to the new . |||2015-06-04 18:01:43|||0:0:0:0:0:0:0:1
164|||169|||so you mean we do add instead of update, right? |||2015-06-04 18:02:52|||0:0:0:0:0:0:0:1
169|||180|||add the role mapping. the user_role table, that should be all that we needed. |||2015-06-04 18:05:22|||0:0:0:0:0:0:0:1
180|||190|||update the user role table for now. add new entry, clean it up over later??|||2015-06-04 18:05:57|||0:0:0:0:0:0:0:1
190|||213|||the purpose of doing is for rollbacking|||2015-06-04 18:06:52|||0:0:0:0:0:0:0:1
213|||224|||right, but ?? , I don't want user to do validation in QA, because QA has mock auth, so I want|||2015-06-04 18:08:36|||0:0:0:0:0:0:0:1
224|||238|||so I want them use in UAT env, and enable the devmon auth , so they use prod login to actually verify, they can able to login. |||2015-06-04 18:10:09|||0:0:0:0:0:0:0:1
238|||247|||cc logins. ok|||2015-06-04 18:10:48|||0:0:0:0:0:0:0:1
247|||265|||TC locally tested the UAT link, and login, password chaning are working. |||2015-06-04 18:12:37|||0:0:0:0:0:0:0:1
265|||281|||there was one open question though, because this morning Nanda product?? that new enhancement requests made by |||2015-06-04 18:15:18|||0:0:0:0:0:0:0:1
281|||289|||operations, they were asking when we could release those |||2015-06-04 18:16:34|||0:0:0:0:0:0:0:1
289|||296|||so I give them options basically, either, we defer everything by one week. |||2015-06-04 18:18:19|||0:0:0:0:0:0:0:1
296|||308|||and include all other items, or we release first and then maybe ?? a week later, we release other|||2015-06-04 18:19:53|||0:0:0:0:0:0:0:1
308|||1318||| |||2015-06-04 18:17:22|||0:0:0:0:0:0:0:1
1318|||2468||| |||2015-06-04 17:58:52|||0:0:0:0:0:0:0:1
2468|||3456||| |||2015-06-04 17:58:52|||0:0:0:0:0:0:0:1

OCPP是Open Charge Point Protocol(开放式充电桩协议)的简称。它是一种开放的通信协议,用于充电桩与其他系统(如后台管理系统)之间的数据交互。 "steve"可能是指OCPP标准中定义的充电站操作员(CSO)的一个实例。充电站操作员是指负责管理、运营充电站网络的组织或个人。 通过OCPP,steve或其他充电站操作员可以与充电桩进行双向通信,实现多种功能。首先,OCPP提供了充电桩的远程监控和控制能力。steve可以远程查看充电桩的状态和充电过程,并及时采取措施来解决故障或支持用户。同时,steve可以通过OCPP下发指令来对充电桩进行控制,例如启动、停止充电等。 其次,OCPP还支持充电数据的收集和管理。steve可以通过OCPP接收来自充电桩的实时数据,如充电状态、充电功率等,用于后续的统计分析和计费。此外,steve还可以通过OCPP将充电桩的状态和数据发送给后台管理系统,实现对充电站网络的监管和管理。 此外,OCPP还提供了一致的充电桩接口规范,使得不同厂商生产的充电桩可以与不同的充电站操作员进行互操作。这种互操作性不仅有助于推动充电基础设施的建设和发展,同时也为用户提供了更多充电选择的可能。 总的来说,OCPP是一种重要的充电桩通信协议,可以实现充电桩与操作员之间的数据交互和功能扩展。通过OCPP,steve及其他充电站操作员可以灵活地管理、控制充电桩网络,提供更好的服务和用户体验。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值