Dear All, Requesting your help on following issue:
I am trying to deploy Multi Node OpenStack (Liberty) env and following exact instructions given at following link: http://docs.openstack.org/liberty/install-guide-ubuntu/ After Keystone configuration, while trying to verify its operation and generating token, facing following error: Command: openstack --os-auth-url http://controller:35357/v3 --os-project-domain-id default --os-user-domain-id default --os-project-name admin --os-username admin --os-auth-type password token issue Error: An unexpected error prevented the server from fulfilling your request. (HTTP 500) (Request-ID: req-c89801db-f8de-457b-8fc5-df0d3c72d44e) Keystone log (/var/log/apache2/keystone.log) shows following: 2016-02-12 11:50:48.044811 2016-02-12 11:50:48.0442808 INFO keystone.common.wsgi [req-c89801db-f8de-457b-8fc5-df0d3c72d44e - - - - -] POST http://controller:5000/v3/auth/tokens 2016-02-12 11:50:48.363340 2016-02-12 11:50:48.362 2808 INFO keystone.common.kvs.core [req-c89801db-f8de-457b-8fc5-df0d3c72d44e - - - - -] Using default dogpile sha1_mangle_key as KVS region token-driver key_mangler 2016-02-12 11:50:55.692962 2016-02-12 11:50:55.692 2808 WARNING keystone.common.wsgi [req-c89801db-f8de-457b-8fc5-df0d3c72d44e - - - - -] An unexpected error prevented the server from fulfilling your request. Best Regards Ankit Agrawal From: openstack-requ...@lists.openstack.org To: openstack@lists.openstack.org Date: 02/11/2016 05:39 PM Subject: Openstack Digest, Vol 32, Issue 13 Send Openstack mailing list submissions to openstack@lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack or, via email, send a message with subject or body 'help' to openstack-requ...@lists.openstack.org You can reach the person managing the list at openstack-ow...@lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Openstack digest..." Today's Topics: 1. Re: Build SUSE Linux ISO (Georgios Dimitrakakis) 2. Re: Build SUSE Linux ISO (Vladimir Kozhukalov) 3. [Openstack Tacker] Integrating an application in VNF (Basavaraj B) 4. [neutron][monasca] (Rubab Syed) 5. Re: [Openstack Tacker] Integrating an application in VNF (HADDLETON, Robert W (Bob)) 6. Re: Root disk resize down (Alberto Molina Coballes) 7. Re: [Openstack Tacker] Integrating an application in VNF (Basavaraj B) 8. Re: Root disk resize down (Ghe Rivero) 9. Re: Root disk resize down (M?rti?? Jakubovi?s) 10. Re: Root disk resize down (M?rti?? Jakubovi?s) 11. Re: I can't get nova-novncproxy to listen on the specified address (Markus Zoeller) 12. Re: Root disk resize down (Remo Mattei) 13. [Neutron][Monasca] (Rubab Syed) 14. Re: Build SUSE Linux ISO (Dmitry Borodaenko) 15. Re: [CINDER] how to get updated pool info when multi users create volumes on pool configured? (yang, xing) 16. [Trove] Can't get database to initialize (Ludwig Tirazona) 17. Re: [Trove] Can't get database to initialize (Ludwig Tirazona) ---------------------------------------------------------------------- Message: 1 Date: Wed, 10 Feb 2016 14:57:47 +0200 From: Georgios Dimitrakakis <gior...@acmac.uoc.gr> To: <openstack@lists.openstack.org> Subject: Re: [Openstack] Build SUSE Linux ISO Message-ID: <e3447ab853e7f0cec1f6fca6d4163...@acmac.uoc.gr> Content-Type: text/plain; charset=UTF-8; format=flowed I would also be interested to hear when Fuel can be installed on a pre-provisioned CentOS machine. Although I am closely folllowing Mirantis updates it would be great if you could give us a note here on the list when that is possible. Regards, G. > Martin, > > We are currently working on making Fuel totally independent on the > ISO. ISO is going to become nothing more than just a convenient way > to > get everything in a single file. We are currently focusing on package > based delivery approach. So, to make it possible to run Fuel on SUSE > you should build all necessary Fuel RPM packages and publish them to > a > repository. Then you could potentially use this repo while building > SUSE based Fuel ISO.? > > But please be informed that we are on our way to make it possible to > install Fuel on the pre-provisioned CentOS 7 just configuring Fuel > yum > repositories and then running yum install command (and probably some > deployment scripts). So, it will be much easier to implement > Fuel-on-SUSE once this feature (installing Fuel from the repo) is > ready. In about several weeks our current build system will be > significantly re-worked (to make it simpler, more flexible and easier > to use). If it is not a problem, you could postpone your activity for > a while (beginning of March or so) and then contact me directly to > get > detailed info. ?? > > This > > doc?https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > [6] is going to be outdated since Fuel 9.0. > > Vladimir Kozhukalov > > On Wed, Feb 10, 2016 at 1:11 PM, Martin Alonso Victor wrote: > >> Good morning, >> >> I was reading the Fuel documentation and I am interested in the >> eighth point from >> https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F [1] >> And I was thinking if its possible to build a SUSE Linux image >> using the SUSE ISO images. Could I build it? >> >> P.S. I read this too >> https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets >> [2] but I dont know if its still possible to achieve what I want. >> >> Thank you so much. >> >> Kind regards, >> >> Victor >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [3] >> Post to? ? ?: openstack@lists.openstack.org [4] >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [5] > > > > Links: > ------ > [1] https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F > [2] > https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > [4] mailto:openstack@lists.openstack.org > [5] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > [6] > https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > [7] mailto:victor.martinalo...@altran.com ------------------------------ Message: 2 Date: Wed, 10 Feb 2016 16:12:07 +0300 From: Vladimir Kozhukalov <vkozhuka...@mirantis.com> To: Georgios Dimitrakakis <gior...@acmac.uoc.gr> Cc: openstack@lists.openstack.org Subject: Re: [Openstack] Build SUSE Linux ISO Message-ID: <caflqvg58gdfd6it9rxevnt52ryasazqdbz7nedcw1o6gt5a...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Georgios, It is to be possible since Fuel 9.0 which, according to our plans, will be released at the same time with OpenStack Mitaka (in April). Vladimir Kozhukalov On Wed, Feb 10, 2016 at 3:57 PM, Georgios Dimitrakakis <gior...@acmac.uoc.gr > wrote: > I would also be interested to hear when Fuel can be installed on a > pre-provisioned CentOS machine. > > Although I am closely folllowing Mirantis updates it would be great if you > could give us a note here on the list when that is possible. > > Regards, > > G. > > > Martin, >> >> We are currently working on making Fuel totally independent on the >> ISO. ISO is going to become nothing more than just a convenient way to >> get everything in a single file. We are currently focusing on package >> based delivery approach. So, to make it possible to run Fuel on SUSE >> you should build all necessary Fuel RPM packages and publish them to a >> repository. Then you could potentially use this repo while building >> SUSE based Fuel ISO. >> >> But please be informed that we are on our way to make it possible to >> install Fuel on the pre-provisioned CentOS 7 just configuring Fuel yum >> repositories and then running yum install command (and probably some >> deployment scripts). So, it will be much easier to implement >> Fuel-on-SUSE once this feature (installing Fuel from the repo) is >> ready. In about several weeks our current build system will be >> significantly re-worked (to make it simpler, more flexible and easier >> to use). If it is not a problem, you could postpone your activity for >> a while (beginning of March or so) and then contact me directly to get >> detailed info. >> >> This >> >> doc https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets >> [6] is going to be outdated since Fuel 9.0. >> >> Vladimir Kozhukalov >> >> On Wed, Feb 10, 2016 at 1:11 PM, Martin Alonso Victor wrote: >> >> Good morning, >>> >>> I was reading the Fuel documentation and I am interested in the >>> eighth point from >>> https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F [1] >>> And I was thinking if its possible to build a SUSE Linux image >>> using the SUSE ISO images. Could I build it? >>> >>> P.S. I read this too >>> https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets >>> [2] but I dont know if its still possible to achieve what I want. >>> >>> Thank you so much. >>> >>> Kind regards, >>> >>> Victor >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [3] >>> Post to : openstack@lists.openstack.org [4] >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [5] >>> >> >> >> >> Links: >> ------ >> [1] https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F >> [2] https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets >> [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> [4] mailto:openstack@lists.openstack.org >> [5] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> [6] https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets >> [7] mailto:victor.martinalo...@altran.com >> > > > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/b5fba181/attachment-0001.html > ------------------------------ Message: 3 Date: Wed, 10 Feb 2016 19:22:14 +0530 From: Basavaraj B <basavaraj...@gmail.com> To: openstack@lists.openstack.org Subject: [Openstack] [Openstack Tacker] Integrating an application in VNF Message-ID: <CADE=9ars3exbw6v8hrtonwhz8fnppen3ajy_t5ui4z48oaw...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello All, I just want to integrate my sample application which has to run automatically upon VNF instantaiation. And I am using Tacker service as well. Can someone please give me pointers on it. Regards, Basavaraj -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/e1028c32/attachment-0001.html > ------------------------------ Message: 4 Date: Wed, 10 Feb 2016 19:05:54 +0500 From: Rubab Syed <rubab.sye...@gmail.com> To: openstack@lists.openstack.org Subject: [Openstack] [neutron][monasca] Message-ID: <capp7javeb67bc-vnnct+feelfetcole4vjvsvyrr0u214zv...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I'm doing a university project in OpenStack. The aim is to monitor virtual routers per tenant with Monasca(which according to my knowledge hasn't been implemented yet). The initial features would include monitoring of in/out traffic per interface. I'm writing a plugin in Monasca for that purpose. If I'm not wrong, I can fetch the data about routers sitting on different compute nodes(in DVR case) running monasca-agent from Neutron database but will have to devise a mechanism to filter traffic based on tenants and subnets. Is there something already implemented in Neutron that I can use for this purpose? Also, I would really appreciate if you guys tell me some use cases for Openstack's virtual routers monitoring per tenant with Monasca? Thanks, Rubab -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/5f99c95c/attachment-0001.html > ------------------------------ Message: 5 Date: Wed, 10 Feb 2016 08:45:15 -0600 From: "HADDLETON, Robert W (Bob)" <bob.haddle...@nokia.com> To: EXT Basavaraj B <basavaraj...@gmail.com>, <openstack@lists.openstack.org> Subject: Re: [Openstack] [Openstack Tacker] Integrating an application in VNF Message-ID: <56bb4cfb.9080...@alcatel-lucent.com> Content-Type: text/plain; charset="iso-8859-15"; Format="flowed" Hi Basavaraj: The most common way to install an application at deployment time is to run a shell script that uses wget/curl/apt-get/yum to retrieve the binary from a repository and then installs the software and configures/runs it. We don't have any examples of this in the Tacker repo yet because we did not have support for the Heat SoftwareConfig/SoftwareDeployment resources. There is a feature under development to integrate tosca-parser and heat-translator into Tacker, which will also provide the ability to use SoftwareConfig and SoftwareDeployment to simplify what you are trying to do. In the mean time I would recommend something like this as a simple example: user_data: | wget http://repo.url/mybinary ./mybinary Hope this helps Bob On 2/10/2016 7:52 AM, EXT Basavaraj B wrote: > Hello All, > > I just want to integrate my sample application which has to run > automatically upon VNF instantaiation. And I am using Tacker service > as well. > > Can someone please give me pointers on it. > > Regards, > Basavaraj > > > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/4d02519f/attachment-0001.html > -------------- next part -------------- A non-text attachment was scrubbed... Name: bob_haddleton.vcf Type: text/x-vcard Size: 248 bytes Desc: not available URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/4d02519f/attachment-0001.vcf > ------------------------------ Message: 6 Date: Wed, 10 Feb 2016 15:49:00 +0100 From: Alberto Molina Coballes <alb.mol...@gmail.com> To: openstack@lists.openstack.org Subject: Re: [Openstack] Root disk resize down Message-ID: <20160210144900.GA2362@jondalar> Content-Type: text/plain; charset=utf-8 On mi?, feb 10, 2016 at 12:41:42 +0200, M?rti?? Jakubovi?s wrote: > Hello, > > Looks like it is not working, when I try to resize instance I receive: > Server disk was unable to be resized because: Resize to zero disk flavor is > not allowed. > Sorry M?rti??, my previous comment wasn't completely correct. I'm assuming that you're using Ceph as a cinder backend and using instances with the root filesystem defined in a volume, so you want to resize your instances without modify the size of the volume, just modify RAM and vCPU, right? In that case you can define several flavors with 0 GiB of disk size and resize up and down your instances between these flavors, but not with other flavors with a disk size greater than 0 GiB defined. Regards, Alberto ------------------------------ Message: 7 Date: Wed, 10 Feb 2016 20:20:50 +0530 From: Basavaraj B <basavaraj...@gmail.com> To: "HADDLETON, Robert W (Bob)" <bob.haddle...@nokia.com> Cc: openstack@lists.openstack.org Subject: Re: [Openstack] [Openstack Tacker] Integrating an application in VNF Message-ID: <CADE=9AT84G464PmWVGq1xU+W9wpRp6hP6d-qjFprX=gfjp5...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thanks Robert for the update. Regards, Basavaraj On Wed, Feb 10, 2016 at 8:15 PM, HADDLETON, Robert W (Bob) < bob.haddle...@nokia.com> wrote: > Hi Basavaraj: > > The most common way to install an application at deployment time is to run > a shell script that uses wget/curl/apt-get/yum to retrieve the binary from > a repository and then installs the software and configures/runs it. > > We don't have any examples of this in the Tacker repo yet because we did > not have support for the Heat SoftwareConfig/SoftwareDeployment resources. > There is a feature under development to integrate tosca-parser and > heat-translator into Tacker, which will also provide the ability to use > SoftwareConfig and SoftwareDeployment to simplify what you are trying to do. > > In the mean time I would recommend something like this as a simple example: > > user_data: | > wget http://repo.url/mybinary > ./mybinary > > Hope this helps > > Bob > > > > On 2/10/2016 7:52 AM, EXT Basavaraj B wrote: > > Hello All, > > I just want to integrate my sample application which has to run > automatically upon VNF instantaiation. And I am using Tacker service as > well. > > Can someone please give me pointers on it. > > Regards, > Basavaraj > > > _______________________________________________ > 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 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/3a15c644/attachment-0001.html > ------------------------------ Message: 8 Date: Wed, 10 Feb 2016 15:51:38 +0100 From: Ghe Rivero <ghe.riv...@gmail.com> To: openstack@lists.openstack.org Subject: Re: [Openstack] Root disk resize down Message-ID: <20160210145138.15232.95788@kaneda> Content-Type: text/plain; charset="utf-8" There could be situations where resizing (up or down) an instance could be an option (like critical non-ha services although this is a real bad policy) but the proper way to operate a cloud is to spin up and kill as many instances as needed. But if you really need to shrink an instance, it's just not a problem of cloud capabilities. The filesystem of your instance must support it (a no go if it's XFS and in case you use ext4, it can be done in offline mode). Ghe Rivero Quoting M?rti?? Jakubovi?s (2016-02-09 12:00:51) > Hello, > > I can't find documentation about this. > Is it possible to resize instance down when use CEPH as storage? > Right now I try to resize down and I receive error: > > Flavor's disk is too small for requested image. Flavor disk is 42949672960 > bytes, image is 21474836480 bytes. > > OS Liberty, > Ubuntu 14.04 x64, > CEPH 0.94.5 ------------------------------ Message: 9 Date: Wed, 10 Feb 2016 17:11:58 +0200 From: M?rti?? Jakubovi?s <martins-li...@hostnet.lv> To: openstack@lists.openstack.org Subject: Re: [Openstack] Root disk resize down Message-ID: <56bb533e.9050...@hostnet.lv> Content-Type: text/plain; charset=utf-8; format=flowed I would be happy if resize is going to smaller flavor, nova just change CPU and RAM, didn't try to change disk to smaller. But it doesn't work. In search I found that it should work like that, resize with KVM just change CPU and RAM, but disk stay same, if flavor have smaller disk. Maybe this is a bug? Best regards, Martins On 2016.02.10. 16:51, Ghe Rivero wrote: > There could be situations where resizing (up or down) an instance could be an option (like critical non-ha services although this is a real bad policy) but the proper way to operate a cloud is to spin up and kill as many instances as needed. But if you really need to shrink an instance, it's just not a problem of cloud capabilities. The filesystem of your instance must support it (a no go if it's XFS and in case you use ext4, it can be done in offline mode). > > Ghe Rivero ------------------------------ Message: 10 Date: Wed, 10 Feb 2016 17:16:10 +0200 From: M?rti?? Jakubovi?s <martins-li...@hostnet.lv> To: openstack@lists.openstack.org Subject: Re: [Openstack] Root disk resize down Message-ID: <56bb543a.20...@hostnet.lv> Content-Type: text/plain; charset=utf-8; format=flowed Yes, with Cinder resize works, and volume resize is separated function. But my issue is when I use VM boot from image, without using cinder, using CEPH directly in nova. On 2016.02.10. 16:49, Alberto Molina Coballes wrote: > Sorry M?rti??, my previous comment wasn't completely correct. > > I'm assuming that you're using Ceph as a cinder backend and using > instances with the root filesystem defined in a volume, so you want > to resize your instances without modify the size of the volume, just > modify RAM and vCPU, right? > > In that case you can define several flavors with 0 GiB of disk size > and resize up and down your instances between these flavors, but not > with other flavors with a disk size greater than 0 GiB defined. > > Regards, > > Alberto ------------------------------ Message: 11 Date: Wed, 10 Feb 2016 17:57:04 +0100 From: "Markus Zoeller" <mzoel...@de.ibm.com> To: openstack@lists.openstack.org Subject: Re: [Openstack] I can't get nova-novncproxy to listen on the specified address Message-ID: <201602101657.u1agvegv014...@d06av04.portsmouth.uk.ibm.com> Content-Type: text/plain; charset="US-ASCII" > ----- Message from Remo Mattei <r...@italy1.com> on Tue, 9 Feb 2016 > 07:21:17 -0800 ----- > > To: > > Ludwig Tirazona <ljtiraz...@gmail.com> > > cc: > > openstack@lists.openstack.org > > Subject: > > Re: [Openstack] I can't get nova-novncproxy to listen on the specified address > > What does the log say under /var/log/nova? > > Inviato da iPhone > > Il giorno 08 feb 2016, alle ore 23:37, Ludwig Tirazona <ljtiraz...@gmail.com > > ha scritto: > Hello Everyone, > > I just can't get my nova-novncproxy to only listen to my public > IP Address. What am I doing wrong? > > Here is the relevant part of my nova.conf: > > [vnc] > enabled = true > vncserver_listen = <my pub IP> > vncserver_proxyclient_address = <my pub IP> > novncproxy_host = <my pub IP> > #novncproxy_base_url = http://my.url:6080/vnc_auto.html > novnproxy_port = 6080 > > Even after doing a "service nova-novncproxy restart", here is the > output of my netstat: > > tcp 0 0 0.0.0.0:6080 0.0.0.0:* > LISTEN nova > > Here is my ps aux: > > 21035 0.0 0.0 232644 49868 ? Ss 15:16 0:00 /usr/bin/ > python /usr/bin/nova-novncproxy --config-file=/etc/nova/nova.conf -- > log-file=/var/log/nova/nova-novncproxy.log > > Any help or pointers are greatly appreciated. Thanks! > !DSPAM:1,56b99a82261194563817953! Hi Ludwig, which Nova version do you use? The two options "novncproxy_host" and "novncproxy_port" are in the "vnc" group with commit [1] since 4th of February 2016. Before of that commit they were in the "DEFAULT" group. The other VNC releated options like "novncproxy_base_url", "enabled", "keymap" and others are in the "VNC" group with commit [2] since 23rd of June 2015. There is a big time gap between those two. [1] https://git.openstack.org/cgit/openstack/nova/commit/?id=11a42d4 [2] https://git.openstack.org/cgit/openstack/nova/commit/?id=380c4d7 Regards, Markus Zoeller (markus_z) ------------------------------ Message: 12 Date: Wed, 10 Feb 2016 09:13:09 -0800 From: Remo Mattei <r...@italy1.com> To: Ghe Rivero <ghe.riv...@gmail.com> Cc: openstack@lists.openstack.org Subject: Re: [Openstack] Root disk resize down Message-ID: <516b883e-2567-4661-8bde-1f7d9c69c...@italy1.com> Content-Type: text/plain; charset=utf-8 ick! yes Ghe, agree but I would not advice this process, even though I have done this many time and works a huge % of the time, it?s not a save solution. parted then will be better if he really needs to address this resize and yes to keep in mind that XFS does not resize down at all. So the best solution as it has been already advised is to spin up a new one and move the data there. Remo > On Feb 10, 2016, at 06:51, Ghe Rivero <ghe.riv...@gmail.com> wrote: > > There could be situations where resizing (up or down) an instance could be an option (like critical non-ha services although this is a real bad policy) but the proper way to operate a cloud is to spin up and kill as many instances as needed. But if you really need to shrink an instance, it's just not a problem of cloud capabilities. The filesystem of your instance must support it (a no go if it's XFS and in case you use ext4, it can be done in offline mode). > > Ghe Rivero > > Quoting M?rti?? Jakubovi?s (2016-02-09 12:00:51) >> Hello, >> >> I can't find documentation about this. >> Is it possible to resize instance down when use CEPH as storage? >> Right now I try to resize down and I receive error: >> >> Flavor's disk is too small for requested image. Flavor disk is 42949672960 >> bytes, image is 21474836480 bytes. >> >> OS Liberty, >> Ubuntu 14.04 x64, >> CEPH 0.94.5 > > _______________________________________________ > 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 > > !DSPAM:1,56bb53ce33081451394549! > ------------------------------ Message: 13 Date: Wed, 10 Feb 2016 22:58:46 +0500 From: Rubab Syed <rubab.sye...@gmail.com> To: openstack@lists.openstack.org Subject: [Openstack] [Neutron][Monasca] Message-ID: <capp7jaupc7poynhduwj0dlqxjwxceth_mfaw+ujk-5hav6y...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I'm doing a university project in OpenStack. The aim is to monitor virtual routers per tenant with Monasca(which according to my knowledge hasn't been implemented yet). The initial features would include monitoring of in/out traffic per interface. I'm writing a plugin in Monasca for that purpose. If I'm not wrong, I can fetch the data about routers sitting on different compute nodes(in DVR case) running monasca-agent from Neutron database but will have to devise a mechanism to filter traffic based on tenants and subnets. Is there something already implemented in Neutron that I can use for this purpose? Also, I would really appreciate if you guys tell me some use cases for Openstack's virtual routers monitoring per tenant with Monasca? Thanks, Rubab -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/dbd35725/attachment-0001.html > ------------------------------ Message: 14 Date: Wed, 10 Feb 2016 13:23:02 -0800 From: Dmitry Borodaenko <dborodae...@mirantis.com> To: Vladimir Kozhukalov <vkozhuka...@mirantis.com> Cc: openstack@lists.openstack.org Subject: Re: [Openstack] Build SUSE Linux ISO Message-ID: <20160210212302.GA17203@localhost> Content-Type: text/plain; charset=us-ascii Georgios, Martin, and others: Once this rework of Fuel build process is done, we'll definitely announce it on openstack-dev ML (using [fuel] tag in the subject, hint hint :). You can also track the progress of this work in the blueprint: https://blueprints.launchpad.net/fuel/+spec/separate-fuel-node-provisioning I will take note to include openstack@ in Fuel 9.0/Mitaka release announcement so that you don't miss it if you're not following openstack-dev. You're also welcome to join us on the #fuel-dev channel and to attend our IRC meetings: https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda Thank you for your interest in Fuel :) -- Dmitry Borodaenko On Wed, Feb 10, 2016 at 04:12:07PM +0300, Vladimir Kozhukalov wrote: > Georgios, > > It is to be possible since Fuel 9.0 which, according to our plans, will be > released at the same time with OpenStack Mitaka (in April). > > Vladimir Kozhukalov > > On Wed, Feb 10, 2016 at 3:57 PM, Georgios Dimitrakakis <gior...@acmac.uoc.gr > > wrote: > > > I would also be interested to hear when Fuel can be installed on a > > pre-provisioned CentOS machine. > > > > Although I am closely folllowing Mirantis updates it would be great if you > > could give us a note here on the list when that is possible. > > > > Regards, > > > > G. > > > > > > Martin, > >> > >> We are currently working on making Fuel totally independent on the > >> ISO. ISO is going to become nothing more than just a convenient way to > >> get everything in a single file. We are currently focusing on package > >> based delivery approach. So, to make it possible to run Fuel on SUSE > >> you should build all necessary Fuel RPM packages and publish them to a > >> repository. Then you could potentially use this repo while building > >> SUSE based Fuel ISO. > >> > >> But please be informed that we are on our way to make it possible to > >> install Fuel on the pre-provisioned CentOS 7 just configuring Fuel yum > >> repositories and then running yum install command (and probably some > >> deployment scripts). So, it will be much easier to implement > >> Fuel-on-SUSE once this feature (installing Fuel from the repo) is > >> ready. In about several weeks our current build system will be > >> significantly re-worked (to make it simpler, more flexible and easier > >> to use). If it is not a problem, you could postpone your activity for > >> a while (beginning of March or so) and then contact me directly to get > >> detailed info. > >> > >> This > >> > >> doc https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > >> [6] is going to be outdated since Fuel 9.0. > >> > >> Vladimir Kozhukalov > >> > >> On Wed, Feb 10, 2016 at 1:11 PM, Martin Alonso Victor wrote: > >> > >> Good morning, > >>> > >>> I was reading the Fuel documentation and I am interested in the > >>> eighth point from > >>> https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F [1] > >>> And I was thinking if its possible to build a SUSE Linux image > >>> using the SUSE ISO images. Could I build it? > >>> > >>> P.S. I read this too > >>> https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > >>> [2] but I dont know if its still possible to achieve what I want. > >>> > >>> Thank you so much. > >>> > >>> Kind regards, > >>> > >>> Victor > >>> _______________________________________________ > >>> Mailing list: > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [3] > >>> Post to : openstack@lists.openstack.org [4] > >>> Unsubscribe : > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [5] > >>> > >> > >> > >> > >> Links: > >> ------ > >> [1] https://wiki.openstack.org/wiki/Fuel#What_is_Fuel.3F > >> [2] https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > >> [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >> [4] mailto:openstack@lists.openstack.org > >> [5] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >> [6] https://docs.fuel-infra.org/fuel-dev/buildsystem.html#build-targets > >> [7] mailto:victor.martinalo...@altran.com > >> > > > > > > _______________________________________________ > > 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 ------------------------------ Message: 15 Date: Wed, 10 Feb 2016 22:39:59 +0000 From: "yang, xing" <xing.y...@emc.com> To: Dilip Sunkum Manjunath <dilip.sunkummanjun...@toshiba-tsip.com>, "'openstack@lists.openstack.org'" <openstack@lists.openstack.org> Cc: "'itzdi...@gmail.com'" <itzdi...@gmail.com> Subject: Re: [Openstack] [CINDER] how to get updated pool info when multi users create volumes on pool configured? Message-ID: <d2e12316.6fd95%xing.y...@emc.com> Content-Type: text/plain; charset="gb2312" Hi Dilip, Can you please clarify your question? If a driver reports both thin_provisioning and thick_provisioning to True and reports free_capacity based on thin provisioning , and you want to provision a thick volume, the scheduler won?t block it and it fail when the driver tries to create volume? If you can describe the exact problem, we can try to find a solution. Thanks, Xing From: Dilip Sunkum Manjunath <dilip.sunkummanjun...@toshiba-tsip.com< mailto:dilip.sunkummanjun...@toshiba-tsip.com>> Date: Monday, February 8, 2016 at 12:52 AM To: "'openstack@lists.openstack.org<mailto:'openstack@lists.openstack.org >'" <openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>> Cc: "'itzdi...@gmail.com<mailto:'itzdi...@gmail.com>'" <itzdi...@gmail.com<mailto:itzdi...@gmail.com>> Subject: Re: [Openstack] [CINDER] how to get updated pool info when multi users create volumes on pool configured? Hi all, The problem what I noticed is, in update stats we send thick and thin volume support as true. This issue can be reproduced. So the over provision and thick and thin parameters are reason, scheduler is not blocking for thick volume based on the capacity if it is thick, it Is passing to the driver which forces driver to handle a particular use case!! I believe this has to handle at the above layer, however it will not know what kind of volume is created using volume types, I think this also has to be considered in scheduler! Any one has a better approach? For this or is it better to write own filters to avoid writing in driver? Thanks Dilip From: Wanghao (S) [mailto:wanghao...@huawei.com] Sent: Thursday, February 04, 2016 11:48 AM To: Dilip Sunkum Manjunath; 'openstack@lists.openstack.org< mailto:'openstack@lists.openstack.org>' Cc: 'itzdi...@gmail.com<mailto:'itzdi...@gmail.com>' Subject: ??: [CINDER] how to get updated pool info when multi users create volumes on pool configured? Hi, Dilip Generally, Cinder scheduler will consume the free_capacity_gb after chose the host for a volume creation, could see the consume_from_volume function in host_manager.py. That keep the pool capacity gb updated correctly when multi users are creating volume. Thanks Wang Hao ???: Dilip Sunkum Manjunath [mailto:dilip.sunkummanjun...@toshiba-tsip.com ] ????: 2016?2?3? 17:50 ???: 'openstack@lists.openstack.org<mailto:'openstack@lists.openstack.org >' ??: 'itzdi...@gmail.com<mailto:'itzdi...@gmail.com>' ??: [Openstack] [CINDER] how to get updated pool info when multi users create volumes on pool configured? Hi All, the get_volume_stats method runs 60 sec once, am using the multi pools configured in it, while creating volumes, if more than one user is creating how will the pool information be reliable which is from pooling job? As it runs once in 60 sec! Am getting the old values and request is failing , has any one faced it before? Thanks Dilip The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the recipient and may contain privileged information. If you are not the intended recipient, please notify the sender and delete the message along with any attachments/annexure/appendices. You should not disclose, copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail are those of the individual sender except where the sender specifically states them to be the views of Toshiba Software India Pvt. Ltd. (TSIP),Bangalore. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Software India Pvt. Ltd, for any loss or damage arising in any way from its use. The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the recipient and may contain privileged information. If you are not the intended recipient, please notify the sender and delete the message along with any attachments/annexure/appendices. You should not disclose, copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail are those of the individual sender except where the sender specifically states them to be the views of Toshiba Software India Pvt. Ltd. (TSIP),Bangalore. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Software India Pvt. Ltd, for any loss or damage arising in any way from its use. -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160210/2fab9e7a/attachment-0001.html > ------------------------------ Message: 16 Date: Thu, 11 Feb 2016 17:55:17 +0800 From: Ludwig Tirazona <ljtiraz...@gmail.com> To: openstack@lists.openstack.org Subject: [Openstack] [Trove] Can't get database to initialize Message-ID: <CAFqim_-xD8yUHEOhBHuOc6Ouo==tz97m7ctmcep7jknz-3q...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello Everyone, It's my first time trying to install Trove. I'm installing under Ubuntu 14.04.3. I did "apt-get install trove-api" with the Ubuntu Liberty repository enabled. (Installed package version: 4.0.0-0ubuntu1~cloud0). I just edited /etc/trove/trove-api.conf to reflect the settings I need (I'm using MySQL), did a "su -s /bin/sh -c "trove-manage db_sync" trove", and got the following errors: http://pastebin.com/rV24CjUd I dropped the database. re-installed, and did a db_sync; I got the same error. Can anybody help, or give some pointers as to what I am doing wrong? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160211/77565131/attachment-0001.html > ------------------------------ Message: 17 Date: Thu, 11 Feb 2016 18:44:51 +0800 From: Ludwig Tirazona <ljtiraz...@gmail.com> To: openstack@lists.openstack.org Subject: Re: [Openstack] [Trove] Can't get database to initialize Message-ID: <cafqim_-9lkruysjb_9yn_mpytbmq+zhddwv5qbjfgwcp3vx...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, Just a follow-up: I switched back to SQLite, that's all I did, and doing a db_sync did NOT produce any errors. Went back to MySQL, did a db_sync, it produced the same errors again. On Thu, Feb 11, 2016 at 5:55 PM, Ludwig Tirazona <ljtiraz...@gmail.com> wrote: > Hello Everyone, > > It's my first time trying to install Trove. I'm installing under > Ubuntu 14.04.3. I did "apt-get install trove-api" with the Ubuntu Liberty > repository enabled. (Installed package version: 4.0.0-0ubuntu1~cloud0). I > just edited /etc/trove/trove-api.conf to reflect the settings I need (I'm > using MySQL), did a "su -s /bin/sh -c "trove-manage db_sync" trove", and > got the following errors: http://pastebin.com/rV24CjUd I dropped the > database. re-installed, and did a db_sync; I got the same error. Can > anybody help, or give some pointers as to what I am doing wrong? Thanks! > -------------- next part -------------- An HTML attachment was scrubbed... URL: < http://lists.openstack.org/pipermail/openstack/attachments/20160211/9a8bcf28/attachment-0001.html > ------------------------------ _______________________________________________ Openstack mailing list openstack@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack End of Openstack Digest, Vol 32, Issue 13 ***************************************** =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
_______________________________________________ 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
