Re: [Openstack] [PackStack][Cinder]Save Volumes in The Compute nodes
Thanks! and Does it need to cinder module to be installed on compute nodes? On Sat, Nov 17, 2018 at 1:13 PM Bernd Bausch <berndbausch@gmail.com> wrote:
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/schedul... .
Here a tip: https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-insta...
Bernd
On Nov 17, 2018, at 8:38, Soheil Pourbafrani <soheil.ir08@gmail.com> wrote:
Hi, I have 8 servers with just local HDD disk. I want to use one server as the controller and network node and the other (7 servers) as the compute node.
I was wondering if it's possible to install PackStack that every compute node to store its volumes in it's HDD local disk? (I guess the Cinder should be installed on every Compute node alongside other settings)
Thanks
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ 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
----- Original Message -----
Thanks! and Does it need to cinder module to be installed on compute nodes?
You will need to run the cinder-volume service in the compute nodes. You will have to set it up manually, though, because Packstack only installs it on the controller. Regards, Javier
On Sat, Nov 17, 2018 at 1:13 PM Bernd Bausch < berndbausch@gmail.com > wrote:
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/schedul... .
Here a tip: https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-insta...
Bernd
On Nov 17, 2018, at 8:38, Soheil Pourbafrani < soheil.ir08@gmail.com > wrote:
Hi,
I have 8 servers with just local HDD disk. I want to use one server as the controller and network node and the other (7 servers) as the compute node.
I was wondering if it's possible to install PackStack that every compute node to store its volumes in it's HDD local disk? (I guess the Cinder should be installed on every Compute node alongside other settings)
Thanks
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ 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
Thanks a lot! On Mon, Nov 26, 2018 at 1:06 PM Javier Pena <jpena@redhat.com> wrote:
------------------------------
Thanks! and Does it need to cinder module to be installed on compute nodes?
You will need to run the cinder-volume service in the compute nodes. You will have to set it up manually, though, because Packstack only installs it on the controller.
Regards, Javier
On Sat, Nov 17, 2018 at 1:13 PM Bernd Bausch <berndbausch@gmail.com> wrote:
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/schedul... .
Here a tip: https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-insta...
Bernd
On Nov 17, 2018, at 8:38, Soheil Pourbafrani <soheil.ir08@gmail.com> wrote:
Hi, I have 8 servers with just local HDD disk. I want to use one server as the controller and network node and the other (7 servers) as the compute node.
I was wondering if it's possible to install PackStack that every compute node to store its volumes in it's HDD local disk? (I guess the Cinder should be installed on every Compute node alongside other settings)
Thanks
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ 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
Hi All, With the current tagged release of Openstack Cinder ( 13.0.1 ) https://github.com/openstack/cinder/releases/tag/13.0.1 we are hitting the below issue https://bugs.launchpad.net/cinder/+bug/1796759 This got fixed with change set https://review.openstack.org/#/c/608768/ which is not a part of the tagged release. Want to know if we can have a new Cinder tag release to incorporate the new fixes. Thanks & Regards, Chhavi Agarwal _______________________________________________ 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
Chhavi, I saw your messages on IRC yesterday and did request a new release. I now see, however, that the fix you want released hasn't been backported yet. I will do the backport and re-request the 13.0.2 release. Thanks! Jay On 11/27/2018 6:52 AM, Chhavi Agarwal wrote:
Hi All,
With the current tagged release of Openstack Cinder ( 13.0.1 ) https://github.com/openstack/cinder/releases/tag/13.0.1we are hitting the below issue
https://bugs.launchpad.net/cinder/+bug/1796759
This got fixed with change set https://review.openstack.org/#/c/608768/which is not a part of the tagged release.
Want to know if we can have a new Cinder tag release to incorporate the new fixes.
Thanks & Regards, Chhavi Agarwal
_______________________________________________ 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
On 11/27/18 4:52 AM, Chhavi Agarwal wrote:
With the current tagged release of Openstack Cinder ( 13.0.1 ) https://github.com/openstack/cinder/releases/tag/13.0.1 we are hitting the below issue
https://bugs.launchpad.net/cinder/+bug/1796759
This got fixed with change set https://review.openstack.org/#/c/608768/ which is not a part of the tagged release.
Want to know if we can have a new Cinder tag release to incorporate the new fixes.
[attempting to cross-post to openstack-discuss] Cinder 13.x releases are OpenStack Rocky, and the upper-constraints for Rocky [1] says oslo.messaging===8.1.2, so there should be no need to backport this fix. Are you trying to run the unit tests when you see this? When I run tox on stable/rocky, it installs 8.1.2 as one of the dependencies, although, to be honest, I'm really not sure how tox knows that that's the right version. Or are you trying to run Cinder from Rocky with newer oslo.messaging, and getting the same symptom as the unit test failures in that bug, when running the cinder services? If so, a) it's an unsupported combination (I believe) and b) you'd (at least) need to update your configuration to remove use of that deprecated rpc_backend option. ~iain [1] https://github.com/openstack/requirements/blob/stable/rocky/upper-constraint...
On 11/27/18 10:52 AM, iain MacDonnell wrote:
On 11/27/18 4:52 AM, Chhavi Agarwal wrote:
With the current tagged release of Openstack Cinder ( 13.0.1 ) https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_cinder_releases_tag_13.0.1&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs&m=_-mGtryix-GE-7_xbOpH7F0ZS4jQxE3RJZ72LghieKQ&s=WMS_BqRFKcnhRVhLF7Etzpoinel262YhUoKvNL19508&e= we are hitting the below issue
This got fixed with change set https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_c_608768_&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=RxYkIjeLZPK2frXV_wEUCq8d3wvUIvDPimUcunMwbMs&m=_-mGtryix-GE-7_xbOpH7F0ZS4jQxE3RJZ72LghieKQ&s=16ZhumVOFprhADv1v553c2wwyMfG84cP0a9Z3VHaVuM&e= which is not a part of the tagged release.
Want to know if we can have a new Cinder tag release to incorporate the new fixes.
[attempting to cross-post to openstack-discuss]
Cinder 13.x releases are OpenStack Rocky, and the upper-constraints for Rocky [1] says oslo.messaging===8.1.2, so there should be no need to backport this fix.
Are you trying to run the unit tests when you see this? When I run tox on stable/rocky, it installs 8.1.2 as one of the dependencies, although, to be honest, I'm really not sure how tox knows that that's the right version.
Ahh, here's how it knows :- $ grep install_command tox.ini install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE:https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/rocky} {opts} {packages} $ ~iain
Or are you trying to run Cinder from Rocky with newer oslo.messaging, and getting the same symptom as the unit test failures in that bug, when running the cinder services? If so, a) it's an unsupported combination (I believe) and b) you'd (at least) need to update your configuration to remove use of that deprecated rpc_backend option.
~iain
On Tue, Nov 27, 2018 at 1:05 PM iain MacDonnell <iain.macdonnell@oracle.com> wrote:
Want to know if we can have a new Cinder tag release to incorporate the new fixes.
[attempting to cross-post to openstack-discuss]
Cinder 13.x releases are OpenStack Rocky, and the upper-constraints for Rocky [1] says oslo.messaging===8.1.2, so there should be no need to backport this fix.
Are you trying to run the unit tests when you see this? When I run tox on stable/rocky, it installs 8.1.2 as one of the dependencies, although, to be honest, I'm really not sure how tox knows that that's the right version.
Ahh, here's how it knows :-
$ grep install_command tox.ini install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/rocky}
{opts} {packages} $
~iain
Yeah, we shouldn't need to backport something like this. We have upper constraints specifically to avoid needing to handle cases like this. Sean
I could see that the Unit tests are run against the latest oslo.messaging from the master, and source tree is old. http://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints... oslo.messaging===9.2.1 [root@ip9-114-192-185 cinder-es]# grep install_command tox.ini install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraint... } {opts} {packages} [root@ip9-114-192-185 cinder-es]# Will get the configuration fixed. Thanks for the clarification. Thanks & Regards, Chhavi Agarwal Cloud System Software Group. From: Sean McGinnis <sean.mcginnis@gmail.com> To: iain.macdonnell@oracle.com Cc: chhagarw@in.ibm.com, openstack@lists.openstack.org, openstack-discuss@lists.openstack.org, jungleboyj@electronicjungle.net, John Griffith <john.griffith8@gmail.com> Date: 11/28/2018 12:39 AM Subject: Re: [Openstack] [Cinder] Cinder New Tag Release On Tue, Nov 27, 2018 at 1:05 PM iain MacDonnell <iain.macdonnell@oracle.com
wrote:
Want to know if we can have a new Cinder tag release to incorporate the new fixes.
[attempting to cross-post to openstack-discuss]
Cinder 13.x releases are OpenStack Rocky, and the upper-constraints for
Rocky [1] says oslo.messaging===8.1.2, so there should be no need to backport this fix.
Are you trying to run the unit tests when you see this? When I run tox on stable/rocky, it installs 8.1.2 as one of the dependencies, although, to be honest, I'm really not sure how tox knows that that's the right version.
Ahh, here's how it knows :- $ grep install_command tox.ini install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraint... } {opts} {packages} $ ~iain Yeah, we shouldn't need to backport something like this. We have upper constraints specifically to avoid needing to handle cases like this. Sean
participants (6)
-
Chhavi Agarwal
-
iain MacDonnell
-
Javier Pena
-
Jay S Bryant
-
Sean McGinnis
-
Soheil Pourbafrani