)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"3289ba4df493b1b6568ea7dbda215aa8c0bdff70","unresolved":false,"context_lines":[{"line_number":9,"context_line":"There is requests from openstack users to have ability to build hybrid clouds"},{"line_number":10,"context_line":"with KVM and ESXi hypervisors (managed by vCenter; DVS is used for network"},{"line_number":11,"context_line":"connectivity). VM on ESXi and VM on KVM should communicate with each other."},{"line_number":12,"context_line":"But there is no support for VMWare vSphere controller on neutron side."},{"line_number":13,"context_line":"Our goal is to fully controll over ESXi hypervisor network (specifically when"},{"line_number":14,"context_line":"vCenter and DVS are used on VMware side) via neutron API."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"da6ed579_d9a031f7","line":12,"range":{"start_line":12,"start_character":16,"end_line":12,"end_character":23},"updated":"2016-01-12 16:58:51.000000000","message":"this is what the project networking-vsphere is for.\n\nBtw, is this the revival of patch [1]?\n\n[1] https://review.openstack.org/#/c/173289/","commit_id":"eaec6e3eb79a236dab91a3f264e62540a5111340"},{"author":{"_account_id":14088,"name":"Andrian Noga","email":"anoga@mirantis.com","username":"anoga"},"change_message_id":"5c1004856307de3c66b20fbf0c8fc4e0cf118515","unresolved":false,"context_lines":[{"line_number":9,"context_line":"There is requests from openstack users to have ability to build hybrid clouds"},{"line_number":10,"context_line":"with KVM and ESXi hypervisors (managed by vCenter; DVS is used for network"},{"line_number":11,"context_line":"connectivity). VM on ESXi and VM on KVM should communicate with each other."},{"line_number":12,"context_line":"But there is no support for VMWare vSphere controller on neutron side."},{"line_number":13,"context_line":"Our goal is to fully controll over ESXi hypervisor network (specifically when"},{"line_number":14,"context_line":"vCenter and DVS are used on VMware side) via neutron API."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"da6ed579_d9e271d5","line":12,"range":{"start_line":12,"start_character":16,"end_line":12,"end_character":23},"in_reply_to":"da6ed579_d9a031f7","updated":"2016-01-12 17:09:49.000000000","message":"Yes, it\u0027s the revival of patch [1]\nIt will be new architecture for mirantis-dvs-vmware\n[1] https://review.openstack.org/#/c/173289/","commit_id":"eaec6e3eb79a236dab91a3f264e62540a5111340"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"07776411804df3836af8c4813a02f39ff74ef302","unresolved":false,"context_lines":[{"line_number":9,"context_line":"There is requests from openstack users to have ability to build hybrid clouds"},{"line_number":10,"context_line":"with KVM and ESXi hypervisors (managed by vCenter; DVS is used for network"},{"line_number":11,"context_line":"connectivity). VM on ESXi and VM on KVM should communicate with each other."},{"line_number":12,"context_line":"But there is no support for VMWare vSphere controller on neutron side."},{"line_number":13,"context_line":"Our goal is to fully controll over ESXi hypervisor network (specifically when"},{"line_number":14,"context_line":"vCenter and DVS are used on VMware side) via neutron API."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"da6ed579_61b53e7c","line":12,"range":{"start_line":12,"start_character":43,"end_line":12,"end_character":53},"updated":"2016-01-14 19:54:39.000000000","message":"This is clearly false, because there is...I have been saying this for a while, and it keeps falling on deaf ears.\n\nI fail to grasp the reason why there\u0027s reluctance to keep open vsphere solutions in one place and provide users with a rationale on how the various solutions compare and contrast.\n\nI am not opposed to Mirantis having the right to host whichever code they want in openstack, but the amount of details provided here does not allow us to make an informed decision that this is the right thing to do, especially when this change is predicated on the inclusion of this under the neutron fold.","commit_id":"3c323b98453479e8063375f867e331909f418c7e"},{"author":{"_account_id":14088,"name":"Andrian Noga","email":"anoga@mirantis.com","username":"anoga"},"change_message_id":"e7b119460c86502c47337e7f98dea985168902c9","unresolved":false,"context_lines":[{"line_number":9,"context_line":"There is requests from openstack users to have ability to build hybrid clouds"},{"line_number":10,"context_line":"with KVM and ESXi hypervisors (managed by vCenter; DVS is used for network"},{"line_number":11,"context_line":"connectivity). VM on ESXi and VM on KVM should communicate with each other."},{"line_number":12,"context_line":"But there is no support for VMWare vSphere controller on neutron side."},{"line_number":13,"context_line":"Our goal is to fully controll over ESXi hypervisor network (specifically when"},{"line_number":14,"context_line":"vCenter and DVS are used on VMware side) via neutron API."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"da6ed579_15d6fcf0","line":12,"range":{"start_line":12,"start_character":43,"end_line":12,"end_character":53},"in_reply_to":"da6ed579_61b53e7c","updated":"2016-01-14 21:08:48.000000000","message":"This version of DVS driver will consists of three main components:\n1.DVS driver placed near neutron-server on each controller\n2.DVS agent. Each instance of DVS agent placed near nova-compute-vmware service in the same way.\n3.vCenter SG driver placed near DVS agent. User can use the driver, can use noop driver (no SG engine) or even implement its own SG driver.\nEach DVS agent controls its own pool of resources (like nova-compute) and has network map in the config file for it.\nDVS driver supports 802.1Q VLAN tagging only. It has not connections to vSphere and info about vSphere at all. User can use multiple agents with its own configuration connected to different vSphere resources and even different independent vSphere farms.\nDVS agent register itself by AMQP on startup and support heartbeat. User can use standard neutron agent-list and neutron agent-show \u003cagent-id\u003e commands to check agent access.\nDVS agent takes port info from port-scan controlled of vCenter DVS instances and/or from dvs-driver notification.\nDVS uses fanout consumers to take notifications about SG changes and network lifecycle. It means that all agents with UP state will create virtual network before port attach or VM creation process. Agent must have a procedure to renew list of current networks on startup process (lifecycle for networks at least).\nDVS agent can CRUID ports itself by RPC trigger. It has port-scan mechanism for other port management type. It uses reverse RPC calls to neutron-server to take the current info for the port update.","commit_id":"3c323b98453479e8063375f867e331909f418c7e"}],"jenkins/jobs/projects.yaml":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"fdb8d9f4c3d096abec336a75b0aa2e79bc5dbb40","unresolved":false,"context_lines":[{"line_number":7815,"context_line":"      - pypi-jobs"},{"line_number":7816,"context_line":"      - translation-jobs"},{"line_number":7817,"context_line":""},{"line_number":7818,"context_line":"- project:"},{"line_number":7819,"context_line":"    name: vmware-dvs"},{"line_number":7820,"context_line":"    node: bare-trusty"},{"line_number":7821,"context_line":"    tarball-site: tarballs.openstack.org"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"da6ed579_39b4fbf0","line":7818,"updated":"2016-01-12 13:39:26.000000000","message":"No need for these changes here, your project does not use any of them.","commit_id":"4aafa26ab6c120ae3385cf0ba1ea27de857c4be2"}]}