[openstack-dev] [Networking-vSphere]

[pravin ghuge]

Hi,
I am trying to configure openstack with VMware as an compute and network
driver as vlan/vxlan. My instances are being created in vCenter, but are
not getting IP.
The bridge created in the neutron node are being created in the vCenter but
they are not attached to any exsi host. I figured that a plugin is required
i.e ovsvapp and NSX and i want to use ovsvapp, But there is no proper
installation doc for the ovsvapp. Please provide the steps to be done on
the openstack neutron/controller/compute nodes and the vCenter(VDS and
uplinks) related to ovsvapp.


Thanks and Regards.

Praveen Ghuge
(askopenstack ID - jarvis@openstack)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Networking-vSphere]

[Carlos Cesario]

Hello team, 

Could someone could confirm if the current 
https://github.com/openstack/networking-vsphere code supports VSS Switch!? It 
seems that the current code only make reference to DVS Switch. 

Thanks in advance! 


best regards, 

Carlos 
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Networking-vSphere] whether support Ocata ?

[Shake Chen]

Hi  Networking-vSphere Team

Networking-vSphere project whether support Ocata. I check the github, only
have tag Mitaka? what about the Ocata?



-- 
Shake Chen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-vsphere] problem with setup regarding specs

[Odintsov Vladislav]

​Hi all.


I'm trying to setup test lab on Openstack Mitaka RDO working simultaneously 
with VLAN and VXLAN network types without SDN. I'm trying to setup ESXi as a 
hypervisor (not only ESXi, but it doesn't matter), and I've got troubles.


My setup:

1 controller node (db, keystone, horizon, nova-{api,conductor,schuduler}, 
glance, memcached, rabbit)

1 network node (neutron-server) (hostname: bc01 in logs/examples)

1 vCenter

2 ESXi hosts

2 neutron-ovsvapp-agents (as described on reference scheme: 
https://wiki.openstack.org/wiki/Neutron/Networking-vSphere - one VM per ESXi 
host; hostnames ovsvapp1, ovsvapp2 in logs/examples)

1 nova-compute VM for managing vSphere cluster (hostname: ovsvapp-nova in 
logs/examples).


When I try to spawn VM, I got error "No valid host was found. There are not 
enough hosts available.".

If I look in nova-compute logs, I see traces:


2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager 
[req-1c94993d-69a0-48d7-ac5f-262f99961b16 18db55ec3559448ba25299cb6bd90504 
bb18be7ce13c44a78419769b4feed0fc - - -] Instance failed network setup after 1 
attempt(s)
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager Traceback (most recent 
call last):
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1570, in 
_allocate_network_async
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager 
bind_host_id=bind_host_id)
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 729, in 
allocate_for_instance
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager 
self._delete_ports(neutron, instance, created_port_ids)
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager 
self.force_reraise()
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager 
six.reraise(self.type_, self.value, self.tb)
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 718, in 
allocate_for_instance
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager 
security_group_ids, available_macs, dhcp_opts)
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager   File 
"/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 305, in 
_create_port
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager raise 
exception.PortBindingFailed(port_id=port_id)
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager PortBindingFailed: 
Binding failed for port ef43e4f0-4db7-405c-b4d5-c621aaa3884b, please check 
neutron logs for more information.
2016-11-07 11:47:12.715 10441 ERROR nova.compute.manager
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager 
[req-1c94993d-69a0-48d7-ac5f-262f99961b16 18db55ec3559448ba25299cb6bd90504 
bb18be7ce13c44a78419769b4feed0fc - - -] [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a] Instance failed to spawn
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a] Traceback (most recent call last):
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2218, in 
_build_resources
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a] yield resources
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2064, in 
_build_and_run_instance
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a] block_device_info=block_device_info)
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a]   File 
"/usr/lib/python2.7/site-packages/nova/virt/vmwareapi/driver.py", line 381, in 
spawn
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a] admin_password, network_info, 
block_device_info)
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a]   File 
"/usr/lib/python2.7/site-packages/nova/virt/vmwareapi/vmops.py", line 724, in 
spawn
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a] metadata)
2016-11-07 11:47:12.716 10441 ERROR nova.compute.manager [instance: 
5ea7de1b-06a2-4ba1-8f54-d00203496f2a]   File 
"/usr/lib/python2.7/site-packages/nova/virt/vmwareapi/vmops.py", line 304, in 

Re: [openstack-dev] [Networking-vSphere]

[Jay Pipes]

On 07/14/2016 09:28 AM, Igor Gajsin wrote:

Thanks for quick reply.


Likewise, apologies for the delayed response! :(


Let's restore the context. I develop plugin for Fuel that uses
Networking-vSphere as the network driver. Next release of Fuel, 9.1 and
maybe 9.X will based on mitaka.


Understood.


For me it means that I have to have a place for commit my changes to
driver. Now I'm working on changing of devstack/plugin.sh to make
possible to install either OVSvApp or VMware DVS driver. But my
ambitions are spread much further.


Land any feature changes in master branch. If you need to backport 
anything to a Mitaka-based source repository due to Mirantis OpenStack 
being based on stable/mitaka code, then you will need to create a 
Mirantis internal branch of the upstream stable/mitaka 
networking-vsphere branch and apply your changes to that internal branch.



I have several ideas how to improve vmware dvs and my question is can I
full-fledged develop it or not?


Of course you can! Only you need to propose these improvements to the 
upstream master branch first.


Best,
-jay


On Thu, Jul 14, 2016 at 3:21 PM, Jay Pipes > wrote:

On 07/14/2016 02:41 AM, Igor Gajsin wrote:

Hi all.

I'm going to add some improvement to Networking-vSphere. There
is the
problem because I'm working with mitaka which already released.
But I
see some commits in the stable/mitaka branch that were made after
release date.

Does it mean, that I can commit new functionality to stable/mitaka
branch and work with it as usual?


Hello Igor!

Generally, no patches should land in a stable branch that provide a
new feature or change existing behaviour. Only bug fixes should be
applied to a stable branch. Can you point to specific patches that
you are referring to?

Thanks!
-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Networking-vSphere]

[Igor Gajsin]

Thanks for quick reply.

Let's restore the context. I develop plugin for Fuel that uses
Networking-vSphere as the network driver. Next release of Fuel, 9.1 and
maybe 9.X will based on mitaka.

For me it means that I have to have a place for commit my changes to
driver. Now I'm working on changing of devstack/plugin.sh to make possible
to install either OVSvApp or VMware DVS driver. But my ambitions are spread
much further.

I have several ideas how to improve vmware dvs and my question is can I
full-fledged develop it or not?

On Thu, Jul 14, 2016 at 3:21 PM, Jay Pipes  wrote:

> On 07/14/2016 02:41 AM, Igor Gajsin wrote:
>
>> Hi all.
>>
>> I'm going to add some improvement to Networking-vSphere. There is the
>> problem because I'm working with mitaka which already released. But I
>> see some commits in the stable/mitaka branch that were made after
>> release date.
>>
>> Does it mean, that I can commit new functionality to stable/mitaka
>> branch and work with it as usual?
>>
>
> Hello Igor!
>
> Generally, no patches should land in a stable branch that provide a new
> feature or change existing behaviour. Only bug fixes should be applied to a
> stable branch. Can you point to specific patches that you are referring to?
>
> Thanks!
> -jay
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Networking-vSphere]

[Jay Pipes]

On 07/14/2016 02:41 AM, Igor Gajsin wrote:

Hi all.

I'm going to add some improvement to Networking-vSphere. There is the
problem because I'm working with mitaka which already released. But I
see some commits in the stable/mitaka branch that were made after
release date.

Does it mean, that I can commit new functionality to stable/mitaka
branch and work with it as usual?


Hello Igor!

Generally, no patches should land in a stable branch that provide a new 
feature or change existing behaviour. Only bug fixes should be applied 
to a stable branch. Can you point to specific patches that you are 
referring to?


Thanks!
-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Networking-vSphere]

[Igor Gajsin]

Hi all.

I'm going to add some improvement to Networking-vSphere. There is the
problem because I'm working with mitaka which already released. But I see
some commits in the stable/mitaka branch that were made after release date.

Does it mean, that I can commit new functionality to stable/mitaka branch
and work with it as usual?
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Networking-vSphere] - changes in nova compute driver

[Gary Kotton]

Hi,
I suggest that the guys who maintain this driver provide you the reasons why 
they maintain the Nova driver like this It is problematic and at times the 
driver can break as it is not in tree.
Thanks
Gary

From: Monotosh Das <monotosh@ericsson.com<mailto:monotosh@ericsson.com>>
Reply-To: OpenStack List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, February 23, 2016 at 1:52 PM
To: OpenStack List 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Networking-vSphere] - changes in nova compute driver

Hi,

In Networking-vSphere (ovsvapp), 'vsphere' is used as nova compute driver. I 
want to know if there is any modification in the default vsphere driver that is 
specific to ovsvapp. If yes, can you give an idea about the changes ?

If not, then how does vsphere driver get to know port group creation is 
complete, as mentioned in the wiki 
(https://wiki.openstack.org/wiki/Neutron/Networking-vSphere) ? In the code 
(nova/virt/vmwareapi/vmops.py : spawn() ), it appears that VM is created first, 
then neutron is updated about the nic, and then VM is powered on. It doesn't 
wait for any event before powering on the VM.

Some clarification about this will be very helpful,


Thanks,
Monotosh



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Networking-vSphere] - changes in nova compute driver

[Monotosh Das]

Hi,

In Networking-vSphere (ovsvapp), 'vsphere' is used as nova compute driver. I 
want to know if there is any modification in the default vsphere driver that is 
specific to ovsvapp. If yes, can you give an idea about the changes ?

If not, then how does vsphere driver get to know port group creation is 
complete, as mentioned in the wiki 
(https://wiki.openstack.org/wiki/Neutron/Networking-vSphere) ? In the code 
(nova/virt/vmwareapi/vmops.py : spawn() ), it appears that VM is created first, 
then neutron is updated about the nic, and then VM is powered on. It doesn't 
wait for any event before powering on the VM.

Some clarification about this will be very helpful,


Thanks,
Monotosh



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev