[Openstack] vCPE Live Webinar
Building a vCPE solution that is cost effective, flexible and innovative Date: February 16, 2017 Learn why an Open NFV Orchestration Framework is the most flexible, cost effective and disruptive way to build vCPE solution that can meet market and CSP demands. In this webinar we will share how you can take your vCPE and make it truly open and innovative. The live webinar will include a Tier-1 Service Provider use case with OpenStack, live Q&A session, and all registered users will receive a copy of the slides and videos. Register here: http://bit.ly/2jDYiFq ___ 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
[Openstack] Summit considerations
Dear fellow stackers, OpenStack summits should be open to all, regardless of religion. Effectively this currently means summits cannot be hosted within the US, per my understanding of current US policies. I wish the board can deliver a policy/statement addressing this. Best regards, fellow human, Martin Millnert PS. No partisan/political discussion required. Objective facts will do. DS signature.asc Description: PGP signature ___ 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
[Openstack] [Fuel] Use other NIC
Hi! I am a new user of Fuel and would like to deploy it on a physical SuperMicro machine. Unfortunately I wasn't able to install it via the ISO file since I 've tried several times (with both the community and the Mirantis edition) and every time there is a problem with the boot loader which cannot be installed correctly thus resulting in a non-bootable system. That's the reason I moved on, I installed CentOS and tried to follow the instructions from here: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_install_fuel_master_node.html Even this attempt was without success since the Fuel bootstrap script is looking for connectivity on eth0 which is not connected. The machine is the property of a DataCenter and out of the 4interfaces only the two are cabled and those two are not the first ones but the third and forth. So my CentOS has connectivity on "eno3" and "eno4" devices. So my question is how can I instruct Fuel to look for connectivity on "eno3" rather than on "eth0" or "eno1"? I did try to disable the first two interfaces from the BIOS but couldn't find any option. Then I thought that I could perform a trick and rename the devices but that doesn't seem correct...If there isn't any other option I will try it but I am sure that Fuel has a way to instract the bootstarp script to use a specific device but haven't found it yet. Your help is much appreciated! Thank you, George ___ 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] Summit considerations
Hi Martin, You can find a short official answer to your question: https://www.openstack.org/blog/2017/01/supporting-our-global-community/ Regards, Marton Kiss OpenStack Ambassador On Sun, Jan 29, 2017 at 6:39 PM Martin Millnert wrote: > Dear fellow stackers, > > OpenStack summits should be open to all, regardless of religion. > Effectively this currently means summits cannot be hosted within > the US, per my understanding of current US policies. > > I wish the board can deliver a policy/statement addressing this. > > Best regards, > fellow human, > Martin Millnert > > PS. No partisan/political discussion required. Objective facts will do. DS > ___ > 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 > ___ 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] Summit considerations
Hi Marton, On Sun, Jan 29, 2017 at 07:51:33PM +, Marton Kiss wrote: > Hi Martin, > > You can find a short official answer to your question: > https://www.openstack.org/blog/2017/01/supporting-our-global-community/ > > Regards, > Marton Kiss > OpenStack Ambassador Thanks for the quick response and appropriate message. Best, Martin Millnert signature.asc Description: PGP signature ___ 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] [Fuel] Use other NIC
I've always run it as a VM. In my opinion there's no real need to dedicate hardware to Fuel since it doesn't even need to be running all the time. Once you deploy your cloud you can shut it down until the next time it's needed. That will solve you eth0 problem also. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. On Sun, Jan 29, 2017 at 1:12 PM, Georgios Dimitrakakis wrote: > Hi! > > I am a new user of Fuel and would like to deploy it on a physical > SuperMicro machine. Unfortunately I wasn't able to install it via the ISO > file since I 've tried several times (with both the community and the > Mirantis edition) and every time there is a problem with the boot loader > which cannot be installed correctly thus resulting in a non-bootable > system. That's the reason I moved on, I installed CentOS and tried to > follow the instructions from here: http://docs.openstack.org/deve > loper/fuel-docs/userdocs/fuel-install-guide/install/install_ > install_fuel_master_node.html > > Even this attempt was without success since the Fuel bootstrap script is > looking for connectivity on eth0 which is not connected. > > The machine is the property of a DataCenter and out of the 4interfaces > only the two are cabled and those two are not the first ones but the third > and forth. So my CentOS has connectivity on "eno3" and "eno4" devices. So > my question is how can I instruct Fuel to look for connectivity on "eno3" > rather than on "eth0" or "eno1"? > > I did try to disable the first two interfaces from the BIOS but couldn't > find any option. Then I thought that I could perform a trick and rename the > devices but that doesn't seem correct...If there isn't any other option I > will try it but I am sure that Fuel has a way to instract the bootstarp > script to use a specific device but haven't found it yet. > > Your help is much appreciated! > > Thank you, > > > George > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac > k > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac > k > ___ 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] [Swift] Bug: swift-ring-builder set_weight doesn't work
Hey Alexandr, Thanks for the email. I can help you in this instance, and I'll push up a patch to correct the usage documentation for the long version of the set_weight command. On Sun, Jan 29, 2017 at 8:33 AM, Alexandr Porunov < alexandr.poru...@gmail.com> wrote: > Hello, > > I can't change a weight of the device. > Here is a list of my devices: > > Devices:id region zone ip address port replication ip > replication port name weight partitions balance meta > 0 1 1 host1 6000 host1 > 6000d1 1000.00 10240.00 bla bla1 bla2 > 1 1 1 host1 6000 host1 > 6000d2 1000.00 10240.00 bla bla1 bla2 > 2 1 1 host1 6000 host1 > 6000d3 1000.00 10240.00 bla bla1 bla2 > > Here is what I tried to change a weight: > swift-ring-builder object.builder set_weight --region 1 --zone 1 --ip > host1 --port 6000 --replication-ip host1 --replication-port 6000 --device > d1 --meta "bla bla1 bla2" --weight 1000 > There is a problem with the command as you've sent it. But I agree it isn't obvious from the usage error. Using the long form (--region, --device, etc) is just defining search criteria for what you want to change. Not specifying what you want to change. So in your case above your looking for a device that already has a weight of 1000, and your not specifying what the change it to. To fix your command, you'd need to: swift-ring-builder object.builder set_weight --region 1 --zone 1 --ip host1 --port 6000 --replication-ip host1 --replication-port 6000 --device d1 --meta "bla bla1 bla2" --weight 1024 1000 NOTE: I am sending in the 1000 as the last option. Obviously as these are search terms you don't actually have to send them all in, only the ones that identify the devices or device you want to change. > swift-ring-builder object.builder set_weight r1z1-host1:6000Rhost1:6000 > d1_"bla bla1 bla2" 2000 > The short version above is failing, as you forgot to add the '/' seperator between the port and the device, given your example it should have been: swift-ring-builder object.builder set_weight r1z1-host1:6000Rhost1:6000/d1_"bla bla1 bla2" 2000 NOTE: the '/' before the d1. What your putting in there is just a search for devices to change. You don't have to put the full string in. I guess if you have a tool that will use the full definition then fine. I find when wanting to update just 1 host it's easier to do so via the device id: swift-ring-builder set_weight d1 2000 In both cases it doesn't work and shows the next information: > > swift-ring-builder set_weight > > [ > [--yes] > > > > or > > > > swift-ring-builder set_weight > > --region --zone --ip --port > > --replication-ip --replication-port > > --device --meta --weight > > [--yes] > > This usage isn't been very useful here, as it's missing the actual adding the weight. I'll raise a bug and patch to address this. > > > Where , and are replication ip, hostname > > and port. > > Any of the options are optional in both cases. > > > > Resets the devices' weights. No partitions will be reassigned to or > from > the device until after running 'rebalance'. This is so you can make > > multiple device changes and rebalance them all just once. > > > > Option --yes assume a yes response to all questions. > > > Please, correct me if it is my fault. > > Best regards, > Alexandr > > ___ > 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 > > regards, Matt ___ 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
[Openstack] Finding common version for keystoneauth1 and remote keystone
Hello everyone. I'm working on openstack application. It should works with large range of openstacks (at least from Havana till Pica+) and works on large range of keystoneauth1 clients (at least from Ubuntu's trusty distro versions till Xenial+). I want it to work with any combination of available versions. I use following steps: 1. Autodiscovery of supported versions: def _find_local_versions(): version_filter = partial(re.find, 'v\d+') return filter(version_filter, dir(keystoneauth1.identity)) 2. Discovery of remote versions: r = requests.get(keystone.auth_url) versions = map(lambda x: x['id'], r.json()['versions']['values']) 3. Matching them together (plus my own application's list of supported versions). 4. Use separate code for 'v2' and 'v3' with auto-conversion between 'tenant_name' and 'project_name' for keystoneauth1.identity.v2/v3 Is this a proper way to do it? Is here a better way to do this? Thanks. ___ 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
[Openstack] User Committee IRC Meeting - Monday Jan 30th - Host Needed
Dear UC Community, Our next UC IRC meeting is scheduled for this Monday Jan 30th at 1900 UTC in (freenode) #openstack-meeting. Unfortunately, I have a last-minute conflict and I won’t be able to lead the session. I would like to know if we have any volunteers to drive the session. I have also a proposal to move the meeting for a different day this week which I like it better. Topics to cover: - UC Election - PTG activities from UC members - Boston planning - Open Agenda User Committee OpenStack Jon, Shilla and Edgar ___ 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
