Re: [Openstack] How to connect host network with each tenant network?
2017-06-15 7:01 GMT+00:00 duhongwei : > > Hi guys, > > Now I'm using a vlan based Neutron network and there's no IP overlap. > Meanwhile I want to let the physical hosts be able to access each of the > tenant vlan networks (still keep tenant networks isolated). > > Any ideas? Well, you could create a Neutron port in each tenant network for your host and then add a corresponding vlan interface to it. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [gerrit] Co-authorship/ownership
2017-04-25 13:34 GMT+00:00 Eric Fried : > Howdy folks. > > What's the protocol when a change set has more than one (significant) > contributor? I've seen this "Co-Authored-By" tag in commit messages - > under what circumstances is it necessary/appropriate to use that? What > official or procedural significance does it have, if any? It may be used to decide whether someone may be nominated as an extra ATC for a project, I've only found https://releases.openstack.org/newton/schedule.html#extra-atcs-deadline for an indirect reference. > Is it possible to change the owner of a change set (e.g. if someone else > has become the primary contributor, or if the original owner has left > the project)? Is that recommended? I don't think that this is possible. If the change becomes sufficiently different from the original, you may consider either splitting it up into two patches or resubmitting it as a new change. Otherwise just adding yourself as co-author and resubmitting seems to be the most common practice. > Is there any other process or metadata that applies to this topic? There may be legal (copyright related) issues, but I don't know about that. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Nova connects to rabbitmq on localhost during migrate (ocata)
Sorry for forgetting to CC the ML on my first reply. 2017-04-06 13:19 GMT+00:00 Kim Gert Nielsen : > On Thu, Apr 06, 2017 at 12:49:23PM +0000, Jens Rosenboom wrote: >> 2017-04-06 11:37 GMT+00:00 Kim Gert Nielsen : >> > Hi, >> > >> > I have just test my ocata installation and most of it seems to be fine. >> > But when resizing an instance I get the error: >> > >> > 7447a2-9602-4d15-8196-9151af6a0e86] AMQP server on 127.0.0.1:5672 is >> > unreachable: [Errno 111] ECONNREFUSED. Trying again in 32 seconds. >> > Client port: None >> > >> > on the compute node. The weird thing is that I have configured a >> > transport_url: >> > >> > >> > [DEFAULT] >> ... >> > transport_url = rabbit://openstack:xxx...@openstack2.example.com >> > > Hi, > > Thanks for responding so fast :) > >> This is taken from the nova.conf during creation of your cell, see >> https://docs.openstack.org/developer/nova/cells.html#fresh-install >> Do you have the same config file on your controller-node and was it in >> place when you created the cell. As you see in the docs you can also >> override it in the command. > > I use chef so I have the same config file (With the exception of $myip) > on the controllers and I have made the steps for the cells only I > haven't done any configuration using cells. Oh, a chef user, nice. Do you use your own cookbooks or the ones from upstream? For upstream, I only recently added cells creation here: https://review.openstack.org/#/c/443711/12/Rakefile But that is only a first step in order to get the integration tests working, for a proper deployment one would need to make this idempotent and such. Still I think running Ocata without cells set up will be difficult. > How do you see that this 'localhost' value comes from the cells > misconfiguration ? In fact that was more guessing than seeing. You might want to check your nova_api database and look at the cell_mappings table there to confirm. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Deleting instance in error state does not free resources
2017-03-08 17:57 GMT+01:00 Georgios Dimitrakakis : > Hi all! > > I am setting up an Ocata installation from scratch and my problem is when > some instances come up in ERROR state (for various reasons). > > Since they are not usable when they are deleted they still continue to > consume resources (VCPUs, Number of Instances, RAM etc). This obviously > affects the availability to new VMs. > > The only way is to clean them up using the "nova-manage project > quota_usage_refresh" > > > What could be wrong? Han anyone else encountered this? This is a known issue, see https://bugs.launchpad.net/nova/+bug/1670627 for more information. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Does anybody know something about ceph.com unavailability?!
2016-10-12 20:18 GMT+02:00 Erdősi Péter : > Hello! > > I know, it's not exactly OS question, but I think a lot of us using it with > libvirt, and maybe somebody have info, cause I cannot reach > download.ceph.com and ceph.com either for 3-4 days, and not found anything > about this issue... These sites seem to have been affected by an issue at Dreamhost: http://www.dreamhoststatus.com/2016/10/11/dreamcompute-us-east-1-cluster-service-disruption/ ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Devstack] How to configure SPICE local.conf
2016-09-19 15:50 GMT+02:00 Silvia Fichera : > Hi all, > I'm installing Openstack Mitaka via Devstack. > Since there is a bug in horizon (reported here > https://bugs.launchpad.net/horizon/+bug/1622684 ) Well, the bug is in noVNC really, you can work around it by checking out the SHA mentioned in the bug report in /opt/stack/noVNC and restarting the n-novnc screen. > I'm trying to configure my > setup to work with Spice instead of vnc. I didn't found any guide to write > properly the local.conf to use spice, so I supposed that, in the controller > node I have to disable n-novnc and enable n-spice > > enable_service n-spice > disable_service n-novnc This part works fine for me in an all-in-one deployment. > and in the compute nodes > > NOVA_VNC_ENABLED=False > NOVA_SPICE_ENABLED=True > SPICEAGENT_ENABLED=True > enable_service n-spice > disable_service n-novnc > > I tried in this way but it does not work (for sure there something wrong). > Any suggestion? What exactly does "it does not work" mean? Do you get an URL from "nova get-spice-console _instance_name_ spice-html5"? Can you connect to that URL? Maybe you need to use another IP or allow the port in the security group? ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack][neutron] Why can't create network with vxlan type and physical network at the same time?
2016-09-06 11:17 GMT+02:00 James Guo : > In neutron, it is not permitted to create vxlan network with physical network > option > > In type_tunnel,py, the function validate_provider_aegment executes the > limitation. > > What is the consideration? Neutron has no way of binding the vxlan tunnels to a specific physical network. It uses local_ip as the local endpoint and advertises this address to the other nodes, which will use whatever routing they have configured in order to reach this endpoint. The usual assumption will be that this is a directly connected network for all nodes, but there may be other deployment options. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
