To all who want to participate in the VES project for Danube, here's an update.
* I've had some difficulty finding an open slot for any regular meetings. I would like to propose that we plan to get on the agenda for the MANO WG calls as shown below, to have quick verbal updates as needed on the project. That time should work for all timezones. We can consider some other slot if we need more time to talk, but that's challenging with the number of meetings we have in OPNFV. * The project planning for Danube is at https://wiki.opnfv.org/display/ves/Project+Plan. Any comments to this plan should be received in JIRA (e.g. as edited or new items) or on the wiki (e.g. as new row entries in the plan table) by the end of this week. * Activity in the git repo over the last few weeks have established a base of code for the demos e.g. as I did at OpenStack Barcelona, and other things o vHello_VES.sh<https://git.opnfv.org/cgit/ves/tree/tests/vHello_VES.sh>: the base of the demo I gave (references tosca-vnfd-hello-ves<https://git.opnfv.org/cgit/ves/tree/tests/blueprints/tosca-vnfd-hello-ves> in the blueprints folder and uses the tacker-setup.sh<https://git.opnfv.org/cgit/models/tree/tests/utils/tacker-setup.sh> script from the Models repo). The demo video etc is shown on the page vHello_VES Demo<https://wiki.opnfv.org/display/ves/vHello_VES+Demo> o setenv.sh<https://git.opnfv.org/cgit/ves/tree/tests/utils/setenv.sh>: in the utils folder, sets up the OpenStack environment etc for the tests o Other work in the repo ? vLamp_Ansible_VES.sh<https://git.opnfv.org/cgit/ves/tree/tests/vLamp_Ansible_VES.sh>: work on getting the OpenStack Lampstack blueprint working. Was planned as the basis of the VES demo but a late change in the Lampstack blueprint cause this to stop working on OPNFV... so this will be revisited. ? VES_Reference.sh<https://git.opnfv.org/cgit/ves/tree/tests/VES_Reference.sh>: initial work on getting the "VES Reference VNF" working - which I may abandon as I have now a real working demo as compared to this exploratory type "reference VNF" demo. * I encourage the committers (cc'd) to watch the Gerrit project<https://gerrit.opnfv.org/gerrit/#/q/project:ves> for patches that are being made to the code above. So far I've been pretty much merging patches as they are developed and tested without additional reviews. But your input on them is welcome, so if you want to start watching and commenting as needed I can slow down the merge process to enable that. But first please confirm by email that you will be participating actively as a committer, so I don't unnecessarily slow down development in the repo. * I received a direct request a couple of weeks back from Liyuanzhen to be removed as committer and Dong wenjuan to be added in place. I have yet to see a specific request on that via the tech-discuss list, but just FYI that request is outstanding and when it comes thru I will start a vote of the committers on that. * Finally: I have been pretty much acting as the PTL for this project. Though Alok was intended to take on that role, he's managing the team that is developing the internal implementation of VES for our service assurance team, so his time to lead this as PTL is limited. If anyone out there wants to get actively involved in the project and take on the PTL role, I'm sure we would appreciate that and support you! FYI: OPNFV MANO WG Meeting Details Meeting Times: Weekly 7 AM PDT (15:00 UTC) this week and 7 AM PST (14:00 UTC) after daylight changes next week IRC#opnfv-mano (meetbot is set for meeting minutes) GOTOMEETING: https://global.gotomeeting.com/join/843517045 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United States: +1 (312) 757-3119 United States (toll-free): 1 877 309 2070 Access Code: 843-517-045 Audio PIN: Shown after joining the meeting Meeting ID: 843-517-045 Thanks, Bryan Sullivan | AT&T
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
