- openstack-discuss - lists.openstack.org

Re: [OCTAVIA] How to monitor amphora
by Bedyk, Witold 27 Nov '18

27 Nov '18

Hi everyone, Monasca is the service which offers centralized monitoring and logging. As Joseph has written, you can probably use the monasca-agent and configure the existing system[1] and process[2] checks. If you need Octavia specific metrics, you can instrument your code using monasca-statsd library [3]. Best greetings Witek [1] https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md#syst… [2] https://github.com/openstack/monasca-agent/blob/master/docs/Plugins.md#proc… [3] https://github.com/openstack/monasca-statsd

1 0

[dev] [tc][all] TC office hours is started now on #openstack-tc
by Ghanshyam Mann 27 Nov '18

27 Nov '18

Hi All, TC office hour is started on #openstack-tc channel. Feel free to reach to us for anything you want discuss/input/feedback/help from TC. - TC

1 0

Re: [OCTAVIA] How to monitor amphora
by Joseph Davis 26 Nov '18

26 Nov '18

Hello Sa Pham and others, Just to throw another option in to your discussion, the monasca-agent would also be able to monitor the cpu, memory, etc. on an amphora. Similar to how the Ceilometer agent -> Gnocchi publishing would work, you could then use Monasca services to track usage and set alarms. And Monasca handles storage in a time series database (Cassandra or InfluxDB). https://github.com/openstack/monasca-agent/blob/master/docs/Agent.md has some details, an you can always ask questions in #openstack-monasca. joseph Adam Harwell wrote: I would also note (though I'm guessing you've heard this from Michael already) that logging and metrics for internal amphora data (like Haproxy logs, agent logs, etc) is on our roadmap to officially expose via some mechanism. We discussed possible ways to do this at the last PTG, but we were just waiting on someone to have time to do a blueprint for review. If you'd like to help get support for this upstream, you're welcome (actually, highly encouraged!) to hop into our IRC channel #openstack-lbaas and we can even help you get started. Hope to see you there! --Adam Harwell (rm_work) On Mon, Nov 26, 2018, 10:19 Michael Johnson <johnsomor(a)gmail.com> wrote: > This is an area we have been talking about recently at the PTGs. > > Adding connection log offloading is on our short term road map. > Someone had signed up for that, but has pivoted to work on other > items. > Due to that I can't say if it will make it for Stein or not. If > someone is interested in picking this up, I can help point you to the > documentation of our discussions at the PTGs. If not, I would expect > it to land late in Stein or early in Train. > > As for other monitoring, CPU, etc. this is area we currently leave to > the operator, but would like to do some work on. As mentioned above > gnocchi appears to be a nice time-series database for metrics > collection. We would need to have some design discussions on what and > how to collect the data. As you mentioned, monitoring agents can be > added to the amphora image at build time if the operator would like to > add a local tool set. > > As with most parts of Octavia, we try to make things "plug-able" so > that operators have a choice of tools. Both the log offloading and > metrics should follow that design principle. > > Michael > > On Sun, Nov 25, 2018 at 10:49 PM Gaël THEROND<gael.therond(a)gmail.com> > wrote: >> Hi! >> >> I’ve taken some time to read your presentation and I have to say thank > you for your wonderful work ! It’s pretty much complete and with code > example which is really cool. >> It’s exactly what I was looking for. >> If I could just suggest one thing, it would be to give operators freedom > to choose which logging and which metrics clients they want to use. >> Doing so would avoid having to rely on gnocchi as you would be able to > choose the clients type at amphora build time and specify clients target at > runtime using the amphora-agent. >> On another hand, it might we’ll be tricky to do so as everything is > namespaced into the amphora instance. >> As suggested using gnocchi to store HAProxy logs may well be the easiest > short path actually, I’m wondering if it would be possible for searchlight > to use that logs at some point. >> Anyway, thanks for the awesome job. >> For now I’ll keep it simple and just use the API for basic status. >> >> Kind regards, >> G. >> >> Le lun. 26 nov. 2018 à 04:23, Sa Pham<saphi070(a)gmail.com> a écrit : >>> yes. I have discussed with the Octavia team. PTL Johnson has suggested > me to use gnocchi to store octavia amphora metric. >>> >>> On Wed, Nov 21, 2018 at 3:16 PM Gaël THEROND<gael.therond(a)gmail.com> > wrote: >>>> Hi! Thanks for this material, I’ll have a look at it. >>>> >>>> As our philosophy at work is to always push upstream all our > patchs/features or bug fixes, I won’t modify and keep the source code on > our own and if we need further features like that I think we will rather > push for a Blueprint with all required commits. >>>> Did you already discussed that topic with the Octavia team? >>>> >>>> Thanks a lot. >>>> >>>> Le mer. 21 nov. 2018 à 09:12, Sa Pham<saphi070(a)gmail.com> a écrit : >>>>> Hi, >>>>> >>>>> In Vietnam Openinfra Days 2018, I have a presentation about > monitoring and logging for Octavia Amphora. We have to customize octavia > source code to do this. I send you my presentation slide: > https://drive.google.com/file/d/1dHXExEKrHDg4Cf3D1fBeulLDW_G-txLr/view?usp=… >>>>> Best, >>>>> >>>>> On Wed, Nov 21, 2018 at 3:05 PM Gaël THEROND<gael.therond(a)gmail.com> > wrote: >>>>>> Hi guys, >>>>>> >>>>>> As already discussed I had to test Octavia as our corporate > LoadBalancer solution and it was a success. >>>>>> Thank to everyone on this list that assisted me and especially > Michael Octavia is fully working and without weird nightmare glitches. >>>>>> Now that I validated the technical part of my project, I need to > enter more operationals questions such as what’s the best way to monitor > and log amphora? >>>>>> I would like to be able to get a monitoring and logging agent > installed on the amphora in order to get proper metrics about what’s going > on with the LoadBalancer, is it fully cpu loaded? Is it using all network > resources available, are the file descriptors near the initial limits? How > much xxx HTTP return code the loadBalancer is facing and send those logs to > an ELK or something similar. >>>>>> Do you know if that something that I could achieve by adding more > elements to the image at DIB time or are there any other better > best-practices that I should be aware of ? >>>>>> As Octavia is creating a namespace for each HAProxy process, I am > wandering if it’s even possible. >>>>>> Thanks a lot for your hard work guys. >>>>>> >>>>>> Kind regards, >>>>>> >>>>> -- >>>>> Sa Pham Dang >>>>> Cloud RnD Team - VCCloud >>>>> Phone/Telegram: 0986.849.582 >>>>> Skype: great_bn >>>>> >>>>> >>> -- >>> Sa Pham Dang >>> Cloud RnD Team - VCCloud >>> Phone/Telegram: 0986.849.582 >>> Skype: great_bn >>> >>>

1 0

[openstack-dev] [cyborg] New time for Cyborg weekly IRC meetings
by Nadathur, Sundar 26 Nov '18

26 Nov '18

Hi, The current time for the weekly Cyborg IRC meeting is 1400 UTC, which is 6 am Pacific and 10pm China time. That is a bad time for most people in the call. Please vote in this doodle for what time you prefer. If you need more options, please respond in this thread. [1] https://doodle.com/poll/eqy3hp8hfqtf2qyn Thanks & Regards, Sundar __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[Openstack] Way to see VMs under all tenants by non-admin?
by Ken D'Ambrosio 26 Nov '18

26 Nov '18

Hey, all. I've had a request for a non-admin user to see all the VMs currently running, irrespective of project. I've gone through the policy.json file (this is Juno) and enabled everything I could think of that seemed appropriate, to no avail. Is there any way to do this without granting him flat-out admin? Thanks! -Ken _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

3 3

[all] maintainers/reviewers/committers wanted for tiny projects
by Chris Dent 26 Nov '18

26 Nov '18

I was recently going through the list of things to which I'm trying to pay attention and realized there are quite a few small software projects that are OpenStack-related that could do with additional attention because I'm either the sole or one of few maintainers. Some of these are hosted on OpenStack^wOpendev infra, some not. If you're interested in helping out, please have a look and feel free to ask me questions. Many are in some state of either disrepair or incompleteness because they were adopted from absentee owners. Paste: WSGI middleware management framework https://github.com/cdent/paste This was recently adopted because it had issues with Python 3.7 and there were concerns that OpenStack's continued use might present problems. I've also just inherited the pastedeploy package, and will be migrating it over to github too. It will also need some help. Use Flask instead. WSME: Web Service Made Easy (ha!) http://git.openstack.org/cgit/openstack/wsme For a brief period back in the day, this was the recommended way to make a web service in OpenStack. Soon after that it was abandoned by its maintainers and Lucas Gomez and I were press-ganged into maintaining it. It still gets the occasional patch to fix testing or Python 3 -related bugs. Does anyone still use this? Use Flask instead. microversion-parse: Library and WSGI middleware for parsing microversion headers http://git.openstack.org/cgit/openstack/microversion-parse This was extracted from placement's implementation for handling microversions. It tries to be framework agnostic, but is biased somewhat towards WebOb. It's nominally under the management of the API-SIG but it would be good to see it getting more use and thus more fixes. It's also used in Nova, not sure where else. wsgi-intercept: Intercept socket connection to wsgi applications for testing https://github.com/cdent/wsgi-intercept A convenient way to do functional testing of WSGI applications without needing to run a separate process but while still doing legit HTTP. Is used in nova and placement, and may still be used in the telemetry projects. It's old but very useful. It's at the core of gabbi. gabbi: Declarative HTTP Testing for Python and anything else https://github.com/cdent/gabbi YAML-driven testing of HTTP APIs that makes live _so_ _much_ _easier_. Was developed when I was working on telemetry, and is now central to the functional testing of placement. gabbi-tempest: A tempest plugin for using gabbi https://git.openstack.org/cgit/openstack/gabbi-tempest A tempest plugin + zuul job to make it super easy to use gabbi tests for driving integration tests in OpenStack, by mostly adding some YAML. If you're interested, great! Please let me know or simply start fixing things. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

3 5

[openstack-dev] [Octavia] Multinode setup
by Anna Taraday 26 Nov '18

26 Nov '18

Hello everyone! I'm looking into how to run Octavia services (controller worker, housekeeper, health manager) on several network nodes and get confused with setup guide [1]. Is there any special config option for such case? (controller_ip_port_list probably) What manuals/docs/examples do we have except [2] ? [1] - https://docs.openstack.org/octavia/queens/contributor/guides/dev-quick-star… [2] - https://github.com/openstack/octavia/blob/stable/queens/devstack/samples/mu… -- Regards, Ann Taraday __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

3 2

Re: [Openstack] my ask.openstack.org question has waited for moderator approval for 17 days
by Jimmy McArthur 26 Nov '18

26 Nov '18

Hi all - Just a quick follow up on this... I just discovered a quirky UX bug that might explain some frustration people have been having with the moderation. There were messages dating back to March 2018. Basically, when you click to approve/disapprove/etc... it appears that the queue is cleared. But if you go to the menu and go back to the moderation page (or just reload), you get a whole new batch. My guess is moderators have been thinking they're clearing things out, but not. I know that's what happened to me multiple times over a period of many months. I've since really and truly cleared out the queue. I found about 25 users that were spammers and blocked all of them. I also auto-approved anyone that was a valid poster so they can post without moderation moving forward. Ask.openstack.org is still a valued tool for our community and another way for people to engage outside of the mls. It's full of not just valid questions, but a lot of valid answers. I highly encourage those that are curious about becoming a moderator to check it out and let me know. I'm happy to elevate your user to a moderator if you want to contribute. Cheers, Jimmy > Bernd Bausch <mailto:berndbausch@gmail.com> > October 29, 2018 at 6:16 PM > If there is a shortage of moderators, I volunteer. > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack(a)lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Jacob Burckhardt <mailto:jburckhardt@pdvwireless.com> > October 29, 2018 at 6:03 PM > My question on ask.openstack.org says "This post is awaiting moderation". > > It has been like that for 17 days. If you are a moderator, I'd > appreciate if you'd decide whether to publicly post my question: > > https://ask.openstack.org/en/question/116591/is-there-example-of-using-pyth… > > Thanks. > > -Jacob Burckhardt > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack(a)lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

2 1

[neutron] bug deputy report
by Takashi Yamamoto 26 Nov '18

26 Nov '18

Critical https://bugs.launchpad.net/neutron/+bug/1803745 neutron-dynamic-routing: unit test failures with master branch of neutron High https://bugs.launchpad.net/neutron/+bug/1804180 Neutron ovs cleanup cannot run on Windows https://bugs.launchpad.net/neutron/+bug/1794718 Neutron VPNAAS don't update site connections on python3 https://bugs.launchpad.net/neutron/+bug/1799737 l3 agent external_network_bridge broken with ovs Medium https://bugs.launchpad.net/neutron/+bug/1804327 occasional connection reset on SNATed after tcp retries Low https://bugs.launchpad.net/neutron/+bug/1803723 [fwaas] _is_supported_by_fw_l2_driver method is hard linked to the default ML2/OVS core plugin implementation https://bugs.launchpad.net/neutron/+bug/1804274 Neutron error agreggation interfaces https://bugs.launchpad.net/neutron/+bug/1804259 DB: sorting on elements which are AssociationProxy fails Undecided https://bugs.launchpad.net/neutron/+bug/1802971 tempest volume_boot_pattern and basic_ops running concurrently causing timeouts RFE https://bugs.launchpad.net/neutron/+bug/1804634 [RFE] l3_agent should separate router_info creation logic Incomplete https://bugs.launchpad.net/neutron/+bug/1803919 [L2] dataplane down during ovs-agent restart https://bugs.launchpad.net/neutron/+bug/1804842 When kill(sometines doesn't restart) the ovs switch or restart it in the compute nodes vm conectivity is lost https://bugs.launchpad.net/neutron/+bug/1804173 Metadata proxy server SSL handshake problem if Python >= 3 https://bugs.launchpad.net/neutron/+bug/1802736 Reporting to Jaeger with OSProfiler doesn't work https://bugs.launchpad.net/neutron/+bug/1801738 Assigning a FIP to NLBaaS VIP port doesn't affect Designate https://bugs.launchpad.net/neutron/+bug/1801779 Policy rule rule:create_port:fixed_ips:subnet_id doesn't allow non-admin to create port on specific subnet

1 0

[nova] [placement] placement functional testing
by Chris Dent 26 Nov '18

26 Nov '18

When https://review.openstack.org/#/c/617941/ merges (probably today), nova will be running its functional tests against openstack/placement and the existing unit and functional tests in nova that were solely testing placement will be gone. Tests like those in functional/test_servers.py will still be testing against real placement code, using a PlacementFixture that establishes a in-process placement service and an in-RAM database. If you have changes in progress that use placement anywhere in your functional tests it is quite likely you will have some merge conflicts. I tried to make it so that in most cases you don't need to do anything to have a working placement: If you're using the Intergated Helpers, it ought to just work. But if it doesn't please ask here, or find me in IRC and I can try to help. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[openstack-dev] [glance] about use shared image with each other
by Rambo 26 Nov '18

26 Nov '18

Hi,all Recently, I want to use the shared image with each other.I find it isn't convenient that the producer notifies the consumer via email which the image has been shared and what its UUID is. In other words, why the image api v2 is no provision for producer-consumer communication? To make it is more convenient, if we can add a task to change the member_status from "pending" to "accepted" when we share the image with each other. It is similar to the resize_confirm in Nova, we can control the time interval in config. Can you tell me more about this?Thank you very much! Best Regards Rambo __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

2 3

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage
by Bogdan Dobrelya 26 Nov '18

26 Nov '18

Here is a related bug [1] and implementation [1] for that. PTAL folks! [0] https://bugs.launchpad.net/tripleo/+bug/1804822 [1] https://review.openstack.org/#/q/topic:base-container-reduction > Let's also think of removing puppet-tripleo from the base container. > It really brings the world-in (and yum updates in CI!) each job and each > container! > So if we did so, we should then either install puppet-tripleo and co on > the host and bind-mount it for the docker-puppet deployment task steps > (bad idea IMO), OR use the magical --volumes-from <a-side-car-container> > option to mount volumes from some "puppet-config" sidecar container > inside each of the containers being launched by docker-puppet tooling. On Wed, Oct 31, 2018 at 11:16 AM Harald Jensås <hjensas at redhat.com> wrote: > We add this to all images: > > https://github.com/openstack/tripleo-common/blob/d35af75b0d8c4683a677660646… > > /bin/sh -c yum -y install iproute iscsi-initiator-utils lvm2 python > socat sudo which openstack-tripleo-common-container-base rsync cronie > crudini openstack-selinux ansible python-shade puppet-tripleo python2- > kubernetes && yum clean all && rm -rf /var/cache/yum 276 MB > > Is the additional 276 MB reasonable here? > openstack-selinux <- This package run relabling, does that kind of > touching the filesystem impact the size due to docker layers? > > Also: python2-kubernetes is a fairly large package (18007990) do we use > that in every image? I don't see any tripleo related repos importing > from that when searching on Hound? The original commit message[1] > adding it states it is for future convenience. > > On my undercloud we have 101 images, if we are downloading every 18 MB > per image thats almost 1.8 GB for a package we don't use? (I hope it's > not like this? With docker layers, we only download that 276 MB > transaction once? Or?) > > > [1] https://review.openstack.org/527927 -- Best regards, Bogdan Dobrelya, Irc #bogdando

1 0

[openstack-dev] [nova][placement] Please help to review XenServer vgpu related patches
by Naichuan Sun 26 Nov '18

26 Nov '18

Hi, Sylvain, Jay, Eric and Matt, I saw the n-rp and reshaper patches in upstream have almost finished. Could you help to review XenServer vGPU related patches when you have the time? https://review.openstack.org/#/c/520313/ https://review.openstack.org/#/c/521041/ https://review.openstack.org/#/c/521717/ Thank you very much. BR. Naichuan Sun __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[neutron] LP tag for python 3
by Takashi Yamamoto 26 Nov '18

26 Nov '18

hi, currently we seem to have an official tag "py34" on the LP. and "py35" is documented in the contributor guide. https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#py… i'd like to propose to replace them with "py3" mechanically.

2 1

[Openstack] [OpenStack][Cinder]How config cinder.conf [nova] part for InstanceLocalityFilter
by Soheil Pourbafrani 25 Nov '18

25 Nov '18

Hi, I want to enable InstanceLocalityFiletr for the Cinder. I set scheduler_default_filters = AvailabilityZoneFilter,CapacityFilter,CapabilitiesFilter,InstanceLocality But the document said we should specify an account with privileged rights for Nova in Cinder configuration (configure a keystone authentication plugin in the [nova] section), but I can't find an example for such configuration. Can anyone give an example? _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

1 0

[Openstack] [OpenStack][Cinder] Config Volumes to Store on Compute nodes
by Soheil Pourbafrani 25 Nov '18

25 Nov '18

Hi, I want to configure cinder to store Volumes on the Compute nodes. I know I should use the InstanceLocalityFilter. Suppose we have one Controller and two Compute node, should I install the Cinder on each node (Controller and Compute)? I will be appreciated if you suggest me any instruction about this. Thanks! _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

1 0

[Openstack] [openstack][neutron]Iptables snat not work when securitygroup is on
by 陈炤 25 Nov '18

25 Nov '18

Hi, I am building an openstack all-in-one environment in a CentOS7.4 machine. For some reason I have only one network interface(eth0) and one ip address, so I created a linux bridge(br0), and forwarded datas to eth0 using iptables command: iptables -t nat -A POSTROUTING -s {bridge virtual ip} -j SNAT --to {eth0 ip} But it seems not work. When I ping to 8.8.8.8 from br0 and run tcpdump, I can see that datas can be forwared to eth0 and be sent to 8.8.8.8, but when datas are sent back to eth0, they can not be forwarded to br0. Ip forwarding, net.bridge.bridge-nf-call-iptables and net.bridge.bridge-nf-call-ip6tablesare set to 1. If I close security group by setting securitygroup = false, this rule works fine, but if I use iptables -F instead, the rule is not work. Does the securitygroup have a magic to trap iptables? BR Don _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

2 1

[openstack-dev] [kolla] Berlin summit resume
by Eduardo Gonzalez 24 Nov '18

24 Nov '18

Hi kollagues, During the Berlin Summit kolla team had a few talks and forum discussions, as well as other cross-project related topics [0] First session was ``Kolla project onboarding``, the room was full of people interested in contribute to kolla, many of them already using kolla in production environments whiling to make upstream some work they've done downstream. I can say this talk was a total success and we hope to see many new faces during this release putting features and bug fixes into kolla. Slides of the session at [1] Second session was ``Kolla project update``, was a brief resume of what work has been done during rocky release and some items will be implemented in the future. Number of attendees to this session was massive, no more people could enter the room. Slides at [2] Then forum sessions.. First one was ``Kolla user feedback``, many users came over the room. We've notice a big increase in production deployments and some PoC migrating to production soon, many of those environments are huge. Overall the impressions was that kolla is great and don't have any big issue or requirement, ``it works great`` became a common phrase to listen. Here's a resume of the user feedback needs [3] - Improve operational usage for add, remove, change and stop/start nodes and services. - Database backup and recovery - Lack of documentation is the bigger request, users need to read the code to know how to configure other than core/default services - Multi cells_v2 - New services request, cyborg, masakari and tricircle were the most requested - SElinux enabled - More SDN services such as Contrail and calico - Possibility to include user's ansible tasks during deploy as well as support custom config.json - HTTPS for internal networks Second one was about ``kolla for the edge``, we've meet with Edge computing group and others interested in edge deployments to identify what's missing in kolla and where we can help. Things we've identified are: - Kolla seems good at how the service split can be done, tweaking inventory file and config values can deploy independent environments easily. - Missing keystone federation - Glance cache support is not a hard requirement but improves efficiency (already merged) - Multi cells v2 - Multi storage per edge/far-edge - A documentation or architecture reference would be nice to have. Last one was ``kolla for NFV``, few people came over to discuss about NUMA, GPU, SRIOV. Nothing noticiable from this session, mainly was support DPDK for CentOS/RHEL,OracleLinux and few service addition covered by previous discussions. [0] https://etherpad.openstack.org/p/kolla-stein-summit [1] https://es.slideshare.net/EduardoGonzalezGutie/kolla-project-onboarding-ope… [2] https://es.slideshare.net/EduardoGonzalezGutie/openstack-kolla-project-upda… [3] https://etherpad.openstack.org/p/berlin-2018-kolla-user-feedback [4] https://etherpad.openstack.org/p/berlin-2018-kolla-edge [5] https://etherpad.openstack.org/p/berlin-2018-kolla-nfv __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

3 2

[Openstack] [OpenStack][Glance]Getting instance snapshot result in size 0 byte
by Soheil Pourbafrani 24 Nov '18

24 Nov '18

Hi, I have many instances running on OpenStack and I wanted to export them. So I create a snapshot of an instance and it results in a new record in images in the format of Qcow2 and size of 0 bytes! It just created a volume snapshot of the instance, too. I tried with both command line and horizon but the same results! How can I export instances in the correct way? _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

2 1

[Openstack] [OpenStack][Keystone] the controller is node listening on port 5000
by Soheil Pourbafrani 24 Nov '18

24 Nov '18

Hi, I installed keystone step by step according to the OpenStack Doc <https://docs.openstack.org/keystone/rocky/install/keystone-install-rdo.html> but the http server is not listening on the port 5000! The only difference is my hostname (address) is "controller.a.b" instead of "controller". In verifying part of the document I could do all (like creating a user, project, ....) but after installing glance, I found out the Glance API is not running properly and it's because of Keystone is not listening on port 5000! Here are AUTH variables: export OS_PROJECT_DOMAIN_NAME=Default export OS_USER_DOMAIN_NAME=Default export OS_PROJECT_NAME=admin export OS_USERNAME=admin export OS_PASSWORD=XXX export OS_AUTH_URL=http://controller.a.b:5000/v3 export OS_IDENTITY_API_VERSION=3 export OS_IMAGE_API_VERSION=2 When I try "glance image-list", I got: "http://controller.a.b:9292/v2/images?limit=20&sort_key=name&sort_dir=asc: Unable to establish connection" Here is TCP listening ports: tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1614/master tcp 0 0 0.0.0.0:9191 0.0.0.0:* LISTEN 961/python2 tcp 0 0 0.0.0.0:25672 0.0.0.0:* LISTEN 957/beam.smp tcp 0 0 192.168.0.31:3306 0.0.0.0:* LISTEN 1622/mysqld tcp 0 0 192.168.0.31:2379 0.0.0.0:* LISTEN 963/etcd tcp 0 0 192.168.0.31:11211 0.0.0.0:* LISTEN 952/memcached tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 952/memcached tcp 0 0 192.168.0.31:2380 0.0.0.0:* LISTEN 963/etcd tcp 0 0 0.0.0.0:4369 0.0.0.0:* LISTEN 1/systemd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 953/sshd tcp6 0 0 ::1:25 :::* LISTEN 1614/master tcp6 0 0 :::5000 :::* LISTEN 960/httpd tcp6 0 0 :::5672 :::* LISTEN 957/beam.smp tcp6 0 0 ::1:11211 :::* LISTEN 952/memcached tcp6 0 0 :::80 :::* LISTEN 960/httpd tcp6 0 0 :::22 :::* LISTEN 953/sshd As you can see httpd is listening on port 5000 IPV6, but it's not active for IPV4! Here is keystone.log: 2018-11-24 15:55:59.685 17325 INFO keystone.common.wsgi [req-9fedd505-5d98-4c12-a6ad-967f28c766e7 - - - - -] POST http://controller.a.b:5000/v3/auth/tokens 2018-11-24 15:56:00.275 17327 INFO keystone.common.wsgi [req-ca93da87-1d9f-4611-835c-d6972054b8e1 - - - - -] POST http://controller.a.b:5000/v3/auth/tokens 2018-11-24 15:56:00.929 17328 INFO keystone.common.wsgi [req-cf8c6af8-342d-4b14-9826-ba27e5f2897a 1b96f6b67f08495092e98a9b60476152 b33579097090499499625154e92724ee - default default] GET http://controller.a.b:5000/v3/domains/default 2018-11-24 15:56:14.753 17325 INFO keystone.common.wsgi [req-cca0e4a5-0ef9-40d8-a2f4-56c1f0acafcc 1b96f6b67f08495092e98a9b60476152 b33579097090499499625154e92724ee - default default] POST http://controller.a.b:5000/v3/users 2018-11-24 15:56:14.773 17325 WARNING py.warnings [req-cca0e4a5-0ef9-40d8-a2f4-56c1f0acafcc 1b96f6b67f08495092e98a9b60476152 b33579097090499499625154e92724ee - default default] /usr/lib/python2.7/site-packages/oslo_policy/policy.py:896: UserWarning: Policy identity:create_user failed scope check. The token used to make the request was project scoped but the policy requires ['system'] scope. This behavior may change in the future where using the intended scope is required warnings.warn(msg) Another difference between my system and document is that I use static IP and here are interface settings: TYPE="Ethernet" PROXY_METHOD="none" BROWSER_ONLY="no" BOOTPROTO="none" DEFROUTE="yes" IPV4_FAILURE_FATAL="no" IPV6INIT="yes" IPV6_AUTOCONF="yes" IPV6_DEFROUTE="yes" IPV6_FAILURE_FATAL="no" IPV6_ADDR_GEN_MODE="stable-privacy" NAME="enp2s0" UUID="62aa5ce8-64da-41b4-abd3-293fd43584fa" DEVICE="enp2s0" ONBOOT="yes" IPADDR="192.168.0.X" PREFIX="24" GATEWAY="192.168.0.1" DNS1="192.168.0.1" DNS2="8.8.8.8" IPV6_PRIVACY="no" What can be the cause? _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

1 0

[oslo] [config] Using environment variables for config options
by Chris Dent 24 Nov '18

24 Nov '18

I don't recall seeing any specific announcement for this, and I think it is a pretty useful feature, so I thought I'd write about some functionality that I added to oslo.config and was released in 6.7.0. Especially since a lot of people I've mentioned this to thought we already had it. The new version is able to satisfy any registered config option by looking in the process environment for a variable with a predictable name and using its value if set. Options are satisfied in this order: * command line args * environment * config file(s) * everything else (using the new(ish) "sources" concept) In the past it was possible to get config from the environment if the option had been pre-defined as using something in the environment as its default. This new way is much more flexible, and in my experience ideal for container-based environments where you would like an immutable container but want small differences between multiple instances of the same container to be easy to control. Or if you don't need much config at all, you can avoid using a config file entirely. I've been using this with placement, where it's possible to set up a testable placement service with just two environment variables: OS_PLACEMENT_DATABASE__CONNECTION=mysql+pymysql://root:secret@127.0.0.1/placement?charset=utf8 OS_API__AUTH_STRATEGY=noauth2 This shows the pattern of the environment variable name: OS_<config group>__<config opt> There are some docs at https://docs.openstack.org/oslo.config/latest/reference/drivers.html#module… I hope this proves as useful for other people as it has for me. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

3 3

[Openstack-operators] urlopen error [Errno 113] No route to host
by Jawad Ahmed 23 Nov '18

23 Nov '18

Hi all, Has anyone come across this error with utility container.I am running CentOS7 with Queens. After running setup-infrastructure.yml getting into this error while rest is success.Any workaround ? internal_lb_vip_address: 172.25.30.101 fatal: [rmq-db_utility_container-8e503460]: FAILED! => {"changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 113] No route to host>", "redirected": false, "status": -1, "url": " http://172.25.30.101:8181/os-releases/18.0.0/centos-7.5-x86_64/requirements… "} Thank you. -- Greetings, Jawad Ahmed _______________________________________________ OpenStack-operators mailing list OpenStack-operators(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

1 0

[forum] Summary of the "Better expose what we produce" session
by Thierry Carrez 23 Nov '18

23 Nov '18

Hi everyone, The OpenStack community produces a complex landscape of services and other deliverables. Presenting those to the rest of the world in a way that is comprehensive, makes sense and is not overwhelming has been a constant challenge. During this forum session in Berlin we presented the status of various efforts and websites, and discussed next steps. You can see the notes of the session at: https://etherpad.openstack.org/p/BER-better-expose-what-we-produce The plan going forward is to: 1. Continue improving the information presented on openstack.org/software and make more elements driven by the openstack/openstack-map repository YAML files. Immediate next steps include rolling out a new "Overview" page, providing an example YAML template, adding project update video links to the YAML for easier update, and finishing compiling "dependency" information from teams. We will also consider adding diagrams, although it creates a lot of consistency challenges. 2. Make the pages less about the teams and more about the software. That involves creating team pages (or enriching those from the governance website) and link to them instead of displaying information on the software page. 3. Brainstorm ways to move the "drivers list" (currently displayed in the "marketplace" using outdated data from stackalytics Drivers page) directly on the software page 4. For deployment tools, include data from the deployment tool comparison effort (discussed in another session), and consider making room for third-party tools as well. Also as a comparison point see https://kubernetes.io/docs/setup/pick-right-solution/ 5. For SDKs, include non-developed-locally language SDKs in a separate tab, and engage with the groups working on SDK certification / validation to see if there is any additional information we can show. Also as a comparison point see https://kubernetes.io/docs/reference/using-api/client-libraries/ Thanks ! -- Thierry Carrez (ttx)

4 3

Re: [Openstack-operators] Openstack zun on centos???
by Hongbin Lu 23 Nov '18

23 Nov '18

Hi Edoardo, It looks you gets your answer from others. I just want to add a few more comments. We (the Zun team) would like to have CentOS included in our installation guide and I have created a ticket for that: https://blueprints.launchpad.net/zun/+spec/installation-guide-for-centos . It will be picked up by contributors if someone interests to work on it. I expect the steps would be very similar as Ubuntu expect a few necessary tweaks. Right now, there is no Debian or RPM packages for Zun so we instruct users to install from source, which might be a bit painful. I would like to see Zun included in distro packages and I will see if we can recruit contributors to work on that, or I will work on that myself. Best regards, Hongbin On Wed, Nov 14, 2018 at 1:51 PM Ignazio Cassano <ignaziocassano(a)gmail.com> wrote: > Hi Edoardo, > does it mean openstack kolla installs zun using pip ? > I did not find any zun rpm package > Regards > Ignazio > > Il giorno Mer 14 Nov 2018 18:38 Eduardo Gonzalez <dabarren(a)gmail.com> ha > scritto: > >> Hi Cassano, you can use zun in centos deployed by kolla-ansible. >> >> https://docs.openstack.org/kolla-ansible/latest/reference/zun-guide.html >> >> Regards >> >> El mié., 14 nov. 2018 17:11, Ignazio Cassano <ignaziocassano(a)gmail.com> >> escribió: >> >>> Hi All, >>> I'd like to know if openstack zun will be released for centos. >>> Reading documentation at docs.openstack.org only ubuntu installation is >>> reported. >>> Many thanks >>> Ignazio >>> _______________________________________________ >>> OpenStack-operators mailing list >>> OpenStack-operators(a)lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >> _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > _______________________________________________ OpenStack-operators mailing list OpenStack-operators(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

1 0

[placement] update 18-47
by Chris Dent 23 Nov '18

23 Nov '18

HTML: https://anticdent.org/placement-update-18-47.html It's been a while since the last placement update. Summit happened. Seemed pretty okay, except for the food. People have things they'd like to do with placement. # Most Important We're starting to approach the point where we're thinking about the possibility of maybe turning off placement-in-nova. We're not there yet, and as is always the case with these kinds of things, it's the details at the end that present the challenges. As such there are a mass of changes spread around nova, placement, devstack, grenade, puppet and openstack-ansible related to making things go. More details on those below, but what we need is the same as ever: reviews. Don't be shy. If you're not a core or not familiar with placement, reviews are still very helpful. A lot of the patches take the form of "this _might_ be the right way to do this". # What's Changed There is now a placement-manage command which can do database migrations, driven by alembic. This means that the devstack patch which uses the extracted placement can merge soon. Several other testing related (turning on tempest and grenade for placement) changes depend-on that. Matt did a placement-status command which has a no-op we-are-here upgrade check. We've already met the python3 goals (I think?), so I reckon placement is good to go on community-wide goals. Woot. The PlacementFixture that placement provides for other projects to do functional tests with it has merged. There's a patch for [nova using it](https://review.openstack.org/#/c/617941/). The spec for [counting quota usage in placement](https://review.openstack.org/#/c/509042/) has been revived after learning at summit that a proposed workaround that didn't use placement wasn't really all that good for people using cells v2. # Bugs * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb): 17. +1. * [In progress placement bugs](https://goo.gl/vzGGDQ) 13. +2 # Specs Summit and U.S. Thanksgiving has disrupted progress on some of these, but there are still plenty of specs awaiting their future. _Many_ of these have unaddressed negative review comments. * <https://review.openstack.org/#/c/544683/> Account for host agg allocation ratio in placement (Still in rocky/) * <https://review.openstack.org/#/c/595236/> Add subtree filter for GET /resource_providers * <https://review.openstack.org/#/c/597601/> Resource provider - request group mapping in allocation candidate * <https://review.openstack.org/#/c/549067/> VMware: place instances on resource pool (still in rocky/) * <https://review.openstack.org/#/c/555081/> Standardize CPU resource tracking * <https://review.openstack.org/#/c/599957/> Allow overcommit of dedicated CPU (Has an alternative which changes allocations to a float) * <https://review.openstack.org/#/c/591037/> Modelling passthrough devices for report to placement * <https://review.openstack.org/#/c/603955/> Nova Cyborg interaction specification. * <https://review.openstack.org/#/c/601596/> supporting virtual NVDIMM devices * <https://review.openstack.org/#/c/603352/> Spec: Support filtering by forbidden aggregate * <https://review.openstack.org/#/c/552924/> Proposes NUMA topology with RPs * <https://review.openstack.org/#/c/569011/> Count quota based on resource class * <https://review.openstack.org/#/c/141219/> Adds spec for instance live resize * <https://review.openstack.org/#/c/612497/> Provider config YAML file * <https://review.openstack.org/#/c/509042/> Propose counting quota usage from placement and API database * <https://review.openstack.org/603545> Resource modeling in cyborg. # Main Themes ## Making Nested Useful Progress is being made on gpu-reshaping for libvirt and xen: * <https://review.openstack.org/#/q/topic:bp/reshape-provider-tree+status:open> Making use of nested is bandwidth-resource-provider: * <https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:…> Somewhat related to nested are a stack of changes to how often the ProviderTree in the resource tracker is checked against placement, and a variety of other "let's make this more right" changes in the same neighborhood: * Stack at: <https://review.openstack.org/#/c/615646/> ## Extraction (There's an [etherpad](https://etherpad.openstack.org/p/placement-extract-stein-4) which tracks some of the work related to extraction. Please refer to that for additional information.) TripleO and OpenStack-Ansible are both working on tooling to install and/or upgrade to extracted placement: * <https://review.openstack.org/#/q/topic:tripleo-placement-extraction> * <https://review.openstack.org/#/q/project:openstack/openstack-ansible-os_pla…> libvirt support for GPU reshaping: * <https://review.openstack.org/#/c/599208/> Grenade and tempest testing for extracted placement: * Extracted placement in devstack: <https://review.openstack.org/600162> * Turning on tests: <https://review.openstack.org/#/c/617565/> * Some fixes to grenade using python3: <https://review.openstack.org/#/c/619728/> A replacement for `placeload` performance testing that was in the `nova-next` job: <https://review.openstack.org/#/c/619248/>. This might be of interest to people trying to do testing of live services without devstack. It starts with a basic node, turns on mysql, runs placement with uwsgi, and does the placeload testing. Note that this found a pretty strange [bug in _ensure_aggregates](https://bugs.launchpad.net/nova/+bug/1804453). Documentation tuneups: * Front page: <https://review.openstack.org/#/c/619273/> * Release-notes: <https://review.openstack.org/#/c/618708/> This is blocked until we refactor the release notes to reflect _now_ better. * The main remaining task here is participating in [openstack-manuals](https://docs.openstack.org/doc-contrib-guide/doc-index.h…. We've been putting off making a decision about os-resource-classes. Anyone have strong opinions? # Other Besides the 20 or so [open changes](https://review.openstack.org/#/q/status:open+project:openstack/pla… in placement itself, and those mentioned above, here are some other changes that may be of interest. * <https://review.openstack.org/#/q/topic:bp/initial-allocation-ratios> Improve handling of default allocation ratios * <https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placeme…> Neutron minimum bandwidth implementation * <https://review.openstack.org/#/c/602160/> Add OWNERSHIP $SERVICE traits * <https://review.openstack.org/#/c/586960/> zun: Use placement for unified resource management * <https://review.openstack.org/#/q/topic:cd/gabbi-tempest-job> Using gabbi-tempest for integration tests. * <https://review.openstack.org/#/q/project:openstack/blazar+topic:bp/placemen…> Blazar using the placement-api * <https://review.openstack.org/619626> Tenks doing some node management, with a bit of optional placement. * <https://review.openstack.org/617273> Extracted placement in loci * <https://review.openstack.org/#/c/613589/> Extracted placement in kolla * <https://review.openstack.org/#/c/613629/> Extracted placement in kolla-ansible # End Lot going on. Thanks to everyone for their contributions. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

RE: [openstack-dev] StarlingX gap analysis to converge with OpenStack master
by Xu, Chenjie 22 Nov '18

22 Nov '18

Hi Miguel, There is another RFE “Add l2pop support for floating IP resources” proposed to Launchpad. This RFE also comes from StarlingX and the link is below: https://bugs.launchpad.net/neutron/+bug/1803494 Could you please help review this RFE? I think this RFE can be added to the gap analysis. What’s more, there is a bug and a RFE relating to l2pop and neutron-dynamic-routing is being written and is expected to be released next week. Best Regards, Xu, Chenjie From: Miguel Lavalle [mailto:miguel@mlavalle.com] Sent: Thursday, November 22, 2018 2:12 AM To: openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>; OpenStack Development Mailing List <openstack-dev(a)lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] StarlingX gap analysis to converge with OpenStack master Hi Stackers, One of the key goals of StarlingX during the current cycle is to converge with the OpenStack projects master branches. In order to accomplish this goal, the Technical Steering Committee put together a gap analysis that shows the specs and patches that need to merge in the different OpenStack projects by the end of Stein. The attached PDF document shows this analysis. Although other projects are involved, most of the work has to be done in Nova, Neutron and Horizon. Hopefully all the involved projects will help StarlingX achieve this important goal. It has to be noted that work is still on-going to refine this gap analysis, so there might be some updates to it in the near future. Best regards Miguel

2 1

[Openstack] Fwd: FOSDEM‘19 Virtualization & IaaS Devroom CfP
by Piotr Kliczewski 22 Nov '18

22 Nov '18

A friendly reminder that Cfp is due by 1st of December. Please submit your proposal using: https://penta.fosdem.org/submission/FOSDEM19 ---------- Forwarded message --------- From: Piotr Kliczewski <pkliczew(a)redhat.com> Date: Wed, Oct 17, 2018 at 9:41 AM Subject: [Openstack] FOSDEM‘19 Virtualization & IaaS Devroom CfP To: <openstack(a)lists.openstack.org> We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2019, to be hosted on February 2nd 2019. This year will mark FOSDEM’s 19th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. FOSDEM will be held once again in Brussels, Belgium, on February 2nd & 3rd, 2019. This devroom is a collaborative effort, and is organized by dedicated folks from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, and Foreman. We would like to invite all those who are involved in these fields to submit your proposals by December 1st, 2018. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 1 December 2019 Acceptance notifications: 14 December 2019 Final schedule announcement: 21 December 2019 Devroom: 2nd February 2019 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will be recorded and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend FOSDEM and deliver your presentation. We will not consider proposals from prospective speakers who are unsure whether they will be able to secure funds for travel and lodging to attend FOSDEM. (Sadly, we are not able to offer travel funding for prospective speakers.) Speaker Mentoring Program As a part of the rising efforts to grow our communities and encourage a diverse and inclusive conference ecosystem, we're happy to announce that we'll be offering mentoring for new speakers. Our mentors can help you with tasks such as reviewing your abstract, reviewing your presentation outline or slides, or practicing your talk with you. You may apply to the mentoring program as a newcomer speaker if you: Never presented before or Presented only lightning talks or Presented full-length talks at small meetups (<50 ppl) Submission Guidelines Mentored presentations will have 25-minute slots, where 20 minutes will include the presentation and 5 minutes will be reserved for questions. The number of newcomer session slots is limited, so we will probably not be able to accept all applications. You must submit your talk and abstract to apply for the mentoring program, our mentors are volunteering their time and will happily provide feedback but won't write your presentation for you! If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. How to Apply In addition to agreeing to video recording and confirming that you can attend FOSDEM in case your session is accepted, please write "speaker mentoring program application" in the "Submission notes" field, and list any prior speaking experience or other relevant information for your application. Call for Mentors Interested in mentoring newcomer speakers? We'd love to have your help! Please email iaas-virt-devroom at lists.fosdem.org with a short speaker biography and any specific fields of expertise (for example, KVM, OpenStack, storage, etc.) so that we can match you with a newcomer speaker from a similar field. Estimated time investment can be as low as a 5-10 hours in total, usually distributed weekly or bi-weekly. Never mentored a newcomer speaker but interested to try? As the mentoring program coordinator, email Brian Proffitt[3] and he will be happy to answer your questions! Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance watching time for the speakers, and helping with video for the devroom. Please contact Brian Proffitt, for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17> https://penta.fosdem.org/submission/FOSDEM19 [2] iaas-virt-devroom at lists.fosdem.org <https://lists.fosdem.org/listinfo/fosdem> [3] bkp at redhat.com <https://lists.fosdem.org/listinfo/fosdem> _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

1 0

[Openstack-operators] openstack-annsible networking layout before running playbooks
by Jawad Ahmed 22 Nov '18

22 Nov '18

Hi all, I am deploying openstack-ansible in test environment where I need to use br-mgmt bridge for both storage and management traffic (same bridge for both) so that container interfaces eth1 and eth2 will connect to br-mgmt for mgmt and storage traffic at same time.Does it make sense if I ll setup provider networks openstack_user_config.yml as below? tunnel_bridge: "br-vxlan" //separate bridge for vxlan though management_bridge: "br-mgmt" provider_networks: - network: container_bridge: "br-mgmt" container_type: "veth" container_interface: "eth1" ip_from_q: "container" type: "raw" group_binds: - all_containers - hosts is_container_address: true is_ssh_address: true - network: container_bridge: "br-mgmt" container_type: "veth" container_interface: "eth2" ip_from_q: "storage" type: "raw" group_binds: - glance_api - cinder_api - cinder_volume - nova_compute Help would be appreciated. -- Greetings, Jawad Ahmed _______________________________________________ OpenStack-operators mailing list OpenStack-operators(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

2 1

[openstack-dev][tacker] seeking feedback for HealVnfRequest implementation
by Shewale, Bhagyashri 22 Nov '18

22 Nov '18

Hi All, As discussed in the summit, "vdu_autoheal" monitoring policy action implementation should be as per ETSI standard HealVnfRequest interface [1] (refer comment given on patch https://review.openstack.org/#/c/612595/9 ) Started working on the same but have some quires so needs some feedback and inputs. As per the ETSI doc [1] the data model for HealVnfRequest contains two request parameters (cause anddditionalParams) (Check section: 5.5.2.9 Type: HealVnfReques from [1]) The Request Payload for HealVnfRequest (ETSI data structure: HealVnfRequest) should be the dictionary as mentioned in [2] (Check section: Healing VNFs Using ETSI API from [2]) But the “addtionalParams” parameter should be part of "HealVnfOpConfig” and that expects two parameters (cause and parameter) as mentioned in [3] (Check section: 7.1.5.6 HealVnfOpConfig information element from [3]) So accordingly I have designed the request data for vdu_autoheal monitoring policy action as below: Heal Request Data for monitoring: { "cause": "", "additionalParams": [ {“parameter”: <Resource name given in the vnfd template for eg. VDU1>, “cause”: [<Reason for failure of the resource>]}, {“parameter”: <Resource name given in the vnfd template for eg. CP1>, “cause”: [<Reason for failure of the resource]} ] } Please let me know the opinion about the same. Also "HealVnfOpConfig” having type as “tosca.datatypes.nfv.VnfHealOperationConfiguration” as per the ONAP [4] and the schema for that is as mentioned below: Schema: tosca.datatypes.nfv.VnfHealOperationConfiguration derived_from: tosca.datatypes.Root properties: #parameters: #modeled as part of the operation parameter list causes: type: list entry_schema: type: string so does that mean we can accepts this request in tosca template for HealVnfRequest? [1]: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.05.01_60/gs_NFV… [2]: https://www.cisco.com/c/en/us/td/docs/net_mgmt/elastic_services_controller/… [3]: https://www.etsi.org/deliver/etsi_gs/NFV-IFA/001_099/011/02.01.01_60/gs_NFV… [4]: https://onap.readthedocs.io/en/beijing/submodules/modeling/modelspec.git/do… Regards, Bhagyashri Shewale Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged,confidential, and proprietary data. If you are not the intended recipient,please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.

1 0

[openstack-dev] [ZUN] [kuryr-libnetwork]
by Rania Adouni 21 Nov '18

21 Nov '18

Hi everyone, I was trying to create container but I just ended up by this error : *Docker internal error: 500 Server Error: Internal Server Error ("failed to update store for object type *libnetwork.endpointCnt: dial tcp 192.168.1.20:2379 <http://192.168.1.20:2379>: connect: connection refused").* Then I back to Verify operation of the kuryr-libnetwork, if it work fine or not with command : *docker network create --driver kuryr --ipam-driver kuryr --subnet 10.10.0.0/16 <http://10.10.0.0/16> --gateway=10.10.0.1 test_net * But i get this error : *Error response from daemon: failed to update store for object type *libnetwork.endpointCnt: dial tcp 192.168.1.20:2379 <http://192.168.1.20:2379>: connect: connection refused * *Ps: 192.168.1.20 is the address of my controller Node !!* some help will be nice and thanks . Best Regards, Rania Adouni __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

3 4

[openstack-dev] StarlingX gap analysis to converge with OpenStack master
by Miguel Lavalle 21 Nov '18

21 Nov '18

Hi Stackers, One of the key goals of StarlingX during the current cycle is to converge with the OpenStack projects master branches. In order to accomplish this goal, the Technical Steering Committee put together a gap analysis that shows the specs and patches that need to merge in the different OpenStack projects by the end of Stein. The attached PDF document shows this analysis. Although other projects are involved, most of the work has to be done in Nova, Neutron and Horizon. Hopefully all the involved projects will help StarlingX achieve this important goal. It has to be noted that work is still on-going to refine this gap analysis, so there might be some updates to it in the near future. Best regards Miguel

5 7

[k8s] [manila] Manila CSI driver plan
by Tom Barron 21 Nov '18

21 Nov '18

[Robert Vasek, Red Hat colleagues working in this space: please correct any mis-understandings or omissions below] At the Berlin Summit SIG-K8s Working session [1] [2], we agreed to follow up with a note to the larger community summarizing our plan to enable Manila as RWX storage provider for k8s and other container orchestrators. Here it is :) Today there are kubernetes external service providers [3] [4] for Manila with NFS protocol back ends, as well as a way to use an external service provider on the master host in combination with a CSI CephFS node-host plugin [5]. We propose to target an end-to-end, multi-protocol Manila CSI plugin -- aiming at CSI 1.0, which should get support in container orchestrators early in 2019. Converging on CSI will: * provide support for multiple Container Orchestrators, not just k8s * de-couple storage plugin development from k8s life-cycle going forwards * unify development efforts and distributions and set clear expectations for operators and deployers Since manila needs to support multiple file system protocols such as CephFS native and NFS, we propose that work align to the multiplexing CSI architecture outlined here [6]. High level work plan: * Write master host multiplexing controller and node proxy plugins. * Use CephFS node-only plugin from [5] * Write NFS node-only plugin NFS and CephFS are immediate priorities - other file system protocols supported by manila can be added over time if there is interest. -- Tom Barron (irc: tbarron) [1] https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22752/s… [2] https://etherpad.openstack.org/p/sig-k8s-2018-berlin-summit [3] https://github.com/kubernetes-incubator/external-storage [4] https://github.com/kubernetes/cloud-provider-openstack [5] https://www.openstack.org/summit/berlin-2018/summit-schedule/events/21997/d… [6] https://github.com/container-storage-interface/spec/issues/263#issuecomment…

1 0

[tc][python3] next steps for resolution on tracking python 3 releases
by Doug Hellmann 21 Nov '18

21 Nov '18

We currently have 3 changes up for review related to our python 3 testing plans. I think if we line them up in a series it will be clearer how they relate to each other and how we can move ahead with them as a set. I think first we need Zane's resolution [1], since that describes the process we want to use. We're dealing with some final wording questions there, but I think it's very close to ready as it is now. Next, we want Sean's patch that sets the versions we want tested for Stein [2]. Zane proposed that we should have goal champions designated in that change, so we could find someone to do that or we could go ahead and take it as-is and add that information later. Finally, we need a variation of Jeremy's patch that makes the PTI less detailed [3]. One update we could make there is to describe how to find (or link to) the information in the previous patch instead of using any specific versions at all. Thoughts? [1] https://review.openstack.org/#/c/613145/ [2] https://review.openstack.org/#/c/611080/ [3] https://review.openstack.org/#/c/611010/ -- Doug

2 1

OpenStack Summit Berlin Presentation Videos & Slides
by Jimmy McArthur 21 Nov '18

21 Nov '18

Thank you to everyone for a great OpenStack Summit last week in Berlin! As you know, there were hundreds of breakout sessions to catch last week. Videos from the keynote sessions are currently available here [1], and our team is working to get the other breakout session videos loaded as quickly as possible. We're currently expecting all videos to be posted by mid-December, and if we get them up sooner, I'll update this thread. In the meantime, you can watch the keynotes videos [2] and watch this page [3] for updates. Please also note that we sent out a link to all presenters to upload their slides. As they are uploaded, they can be found on the details page for each presentation on the Berlin Summit Schedule [3] (along with videos, as they are processed). Cheers, Jimmy [1] https://www.openstack.org/videos/summits/berlin-2018 [2] https://www.openstack.org/videos/ [3] https://www.openstack.org/summit/berlin-2018/summit-schedule/

4 5

Let's use [dev] for development discussions
by Thierry Carrez 21 Nov '18

21 Nov '18

Hi openstack-discuss, As part of the ML merge, we introduced a number of subject prefixes to help subscribers filter discussions. The most important ones are to use: [dev] For discussions that are purely development-oriented [ops] For discussions that are purely operations-oriented Of course (as we have realized with the amount of cross-posted topics), most discussions benefit from input from all our contributors, whether they come from an development or an operational background. For those, there is no need to apply [dev] and/or [ops] prefixes, just try to be informative by adding the project name, team name or other information instead. You can ping specific populations by adding: [tc] Discussions of interest for TC members [uc] Discussions of interest for UC members [ptl] Discussions of interest for all PTLs [release] Release team, release liaisons and PTLs You can also specifically use (with care): [all] For discussions that should really be of interest to EVERYONE See (and add!) other common subject prefixes at: https://etherpad.openstack.org/p/common-openstack-ml-topics Thanks for your help in making this common list more navigable. -- Thierry Carrez (ttx)

5 7

[manila] no meeting this week
by Tom Barron 21 Nov '18

21 Nov '18

Just a reminder that there will be no manila community meeting this week. Next manila meeting will be Thursday, 29 November, at 1500 UTC in #openstack-meeting-alt on freenode. Agenda here [1] - Feel free to add ... -- Tom Barron (tbarron) [1] https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting

1 0

[openstack-dev] [neutron] [drivers] Cancelling weekly meeting on November 23rd
by Miguel Lavalle 21 Nov '18

21 Nov '18

Dear Neutron team, Due to the Thanksgiving Holiday in the USA, several members of the team will not be able to attend the weekly meeting. Let's cancel it and resume normally on the 30th of November Best regards Miguel __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[infra] [zuul] [placement] Minimizing size/time of test node
by Chris Dent 21 Nov '18

21 Nov '18

I have a work in progress to run a little job in placement that gathers very simple performance numbers on some queries. This is being done as a sort of sanity check. As with many such things it is a bit rough around the edges and I'd like to make it smoother in a variety of ways. The WIP is at https://review.openstack.org/#/c/602484/ One of the ways I'd like to change it is to not rely on devstack. I need only mysql, uwsgi, python and the current revision of placement on the node. The current job uses devstack-minimal as its base but that's overkill and slow. What is the correct base job to use which, as long as I put the files in the right place, will gather the logs I want? Thanks. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

4 5

[openstack-dev] [zun] Failed to create Container
by Rania Adouni 21 Nov '18

21 Nov '18

Hi , I am starting to use zun on openstack pike , and when I try to lunch container with cirros image , I get this reason : Docker internal error: 500 Server Error: Internal Server Error ("legacy plugin: Post http://192.168.1.10:23750/Plugin.Activate: dial tcp 192.168.1.10:23750: connect: connection refused"). you can find here the log on my compute node :https://pastebin.com/nZTiTZiV. some help with this will be great . Best Regards, Rania Adouni __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

3 7

Re: [openstack-dev] [horizon] Do we want new meeting time?
by Ivan Kolodyazhny 21 Nov '18

21 Nov '18

Hi all, Due to the low activity on our weekly meeting, I would like to raise this question again. Do we want a new meeting day and/or time? I'm available any day except Tuesday and Wednesday. I'm going to get some feedback before I create a new poll. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Thu, Apr 5, 2018 at 1:42 PM Ivan Kolodyazhny <e0ne(a)e0ne.info> wrote: > Hi team, > > It's a friendly reminder that we've got voting open [1] until next > meeting. If you would like to attend Horizon meetings, please, select > comfortable options for you. > > [1] https://doodle.com/poll/ei5gstt73d8v3a35 > > Regards, > Ivan Kolodyazhny, > http://blog.e0ne.info/ > > On Wed, Mar 21, 2018 at 6:40 PM, Ivan Kolodyazhny <e0ne(a)e0ne.info> wrote: > >> Hi team, >> >> As was discussed at PTG, usually we've got a very few participants on our >> weekly meetings. I hope, mostly it's because of not comfort meeting time >> for many of us. >> >> Let's try to re-schedule Horizon weekly meetings and get more attendees >> there. I've created a doodle for it [1]. Please, vote for the best time for >> you. >> >> >> [1] https://doodle.com/poll/ei5gstt73d8v3a35 >> >> Regards, >> Ivan Kolodyazhny, >> http://blog.e0ne.info/ >> > > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[openstack-dev] VM stalls with the console log "Exiting boot services and installing virtual address map"
by Srikanth Kumar Lingala 21 Nov '18

21 Nov '18

Hi, I am working with OpenStack stable/pike release in Ubuntu 18.04. When I am trying to spawn VM, which is worked in the earlier OpenStack releases, VM is stalled with the following log in the VM console logs: EFI stub: Booting Linux Kernel... EFI stub: Generating empty DTB EFI stub: Exiting boot services and installing virtual address map... I am observing that VM is in Running status, without any error logs. And, VM is booting with UEFI support. But, I am not able to get VM Console. Earlier I didn't observe this. How can I disable UEFI support, while spawning VM's in OpenStack Nova-Compute. My Libvirt version is 4.0.0. Can someone help me to fix the issue. Regards, Srikanth. -- ---- Srikanth. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[kayobe] Forum summary
by Mark Goddard 21 Nov '18

21 Nov '18

Hi, Thanks to those who attended the kayobe forum session. I'll try to summarise the key points here. The etherpad is here: https://etherpad.openstack.org/p/BER-18-kayobe-feedback-roadmap. - Several people were keen for a Rocky release. We're working on this currently, and aim to make it a small one so that we can move to Stein. - The point was raised that the locally installed environment can be hard to keep in sync, and the installation procedure is too complex. We hope to resolve this for the rocky release via https://storyboard.openstack.org/#!/story/2004252 and https://storyboard.openstack.org/#!/story/2004367. - Documentation is lacking in a few areas. We aim to improve this for rocky: https://storyboard.openstack.org/#!/story/2004360. - Ability to import configuration of an existing deployment from kolla-ansible: https://storyboard.openstack.org/#!/story/2004364 - Document/automate bifrost backup procedure: https://storyboard.openstack.org/#!/story/2004359 A few people also requested that we start a regular IRC meeting. Up to now we've favoured ad-hoc IRC communication, but I tend to agree that the time is right. I'll send out a separate email with a poll. Cheers, Mark

1 0

[Openstack] [OpenStack][Compute-Neutron] Is it possible to create flat network from different NICs
by Soheil Pourbafrani 21 Nov '18

21 Nov '18

Hi, I installed OpenStack on One node (for test) and creating a flat external network I could connect VMs to the provider network (internet). In the production environment, we have 4 NIC on each server and each server (compute node) will run 4 instances. My question is, is it possible to create a separate external network based on each NIC (so 4 external networks) and run each instance using one of them? _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

2 2

[heat] Meeting canceled this week
by Rico Lin 21 Nov '18

21 Nov '18

Hi team Since we just have summit last week, let's not over-occupied all member's time. we shall resume meeting next week -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[keystone][nova] Availability zones and unified limits
by Lance Bragstad 21 Nov '18

21 Nov '18

Unified limits cropped up in a few discussions last week. After describing the current implementation of limits, namely the attributes that make up a limit, someone asked if availability zones were on the roadmap. Ideally, it sounded like they had multiple AZs in a single region, and they wanted to be able to limit usage within the AZ. With the current implementation, regions would be the smallest unit of a deployment they could limit (e.g., limit project Foo to only using 64 compute cores within RegionOne). Instead, the idea would be to limit the number of resources for that project on an AZ within a region. What do people think about adding availability zones to limits? Should it be an official attribute in keystone? What other services would need this outside of nova? There were a few other interesting cases that popped up, but I figured we could start here. I can start another thread if needed and we can keep this specific to discussing limits + AZs. Thoughts?

4 5

Re: [openstack-dev] [nova] Can we deprecate the server backup API please?
by Matt Riedemann 21 Nov '18

21 Nov '18

On 11/18/2018 6:51 AM, Alex Xu wrote: > Sounds make sense to me, and then we needn't fix this strange behaviour > also https://review.openstack.org/#/c/409644/ The same discussion was had in the spec for that change: https://review.openstack.org/#/c/511825/ Ultimately it amounted to a big "meh, let's just not fix the bug but also no one really cares about deprecating the API either". The only thing deprecating the API would do is signal that it probably shouldn't be used. We would still support it on older microversions. If all anyone cares about is signalling not to use the API then deprecation is probably fine, but I personally don't feel too strongly about it either way. -- Thanks, Matt __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

6 5

[scientific-sig] IRC Meeting today 1100 UTC - Summit wash-up, Manila+Lustre
by Stig Telfer 21 Nov '18

21 Nov '18

Hi All - We have a Scientific SIG IRC meeting today at 1100 UTC in channel #openstack-meeting. Everyone is welcome. This week we’ve got the summit activities to digest, plus similar activities at SC. We’d also like to find out if there’s anyone using Manila to manage Lustre filesystems. Today’s agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_November_21st_20… Details on how to join our meetings are here: http://eavesdrop.openstack.org/#Scientific_Working_Group Cheers, Stig

1 0

[openstack-dev] [cyborg] [weekly-meeting]
by Li Liu 20 Nov '18

20 Nov '18

There is no weekly IRC meeting for the week of Nov 21st as most of the people are still recovering from the jetlag after the summit. I will follow up with individuals offline. -- Thank you Regards Li __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[openstack-dev] [tripleo] Feedback about our project at Summit
by Emilien Macchi 20 Nov '18

20 Nov '18

Hi folks, I wasn't at the Summit but I was interested by the feedback people gave about TripleO so I've discussed with a few people who made the trip. I would like to see what actions we can take on short and long term to address it. I collected some thoughts here: https://etherpad.openstack.org/p/BER-tripleo-feedback Which is based on https://etherpad.openstack.org/p/BER-deployment-tools-feedback initially. Feel fee to add more feedback if missing, and also comment what was written. If you're aware of some WIP that address the feedback, adjust some wording if needed or just put some links if something exists and is documented already. I believe it is critical to us to listen this feedback and include some of it into our short term roadmap, so we can reduce some frustration that we can hear sometimes. Thanks for your help, -- Emilien Macchi __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[Openstack] how to sync quota usage our of sync in Rocky release
by Manuel Sopena Ballesteros 20 Nov '18

20 Nov '18

Dear Openstack community, I often have nova complaining that I have exceeded my quota, these normally happens when I node deployment fails and the resources allocated hasn't been released. Before Rocky I used to run the command below to resync, however it looks like it has been removed from Rocky. [root@TEST-openstack-controller ~]# docker exec -it -u root nova_scheduler nova-manage project quota_usage_refresh --project abc29399b91d423088549d7446766573 --user 02132c31dafa4d1d939bd52e0420b975 usage: nova-manage [-h] [--config-dir DIR] [--config-file PATH] [--debug] [--log-config-append PATH] [--log-date-format DATE_FORMAT] [--log-dir LOG_DIR] [--log-file PATH] [--nodebug] [--nopost-mortem] [--nouse-journal] [--nouse-json] [--nouse-syslog] [--nowatch-log-file] [--post-mortem] [--syslog-log-facility SYSLOG_LOG_FACILITY] [--use-journal] [--use-json] [--use-syslog] [--version] [--watch-log-file] [--remote_debug-host REMOTE_DEBUG_HOST] [--remote_debug-port REMOTE_DEBUG_PORT] {version,bash-completion,placement,network,cell_v2,db,cell,floating,api_db} ... nova-manage: error: argument category: invalid choice: 'project' (choose from 'version', 'bash-completion', 'placement', 'network', 'cell_v2', 'db', 'cell', 'floating', 'api_db') Any idea how can I refresh the quota usage in Rocky? Thank you very much Manuel Sopena Ballesteros | Big data Engineer Garvan Institute of Medical Research The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010 T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: manuel.sb(a)garvan.org.au<mailto:manuel.sb@garvan.org.au> NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed. _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

2 1