Discussion:
[Openstack] [PackStack][Cinder]Save Volumes in The Compute nodes
Soheil Pourbafrani
2018-11-17 07:38:52 UTC
Permalink
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
Bernd Bausch
2018-11-17 09:43:42 UTC
Permalink
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/scheduler-filters.html.

Here a tip: https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-instance/

Bernd
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
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Soheil Pourbafrani
2018-11-22 19:38:47 UTC
Permalink
Thanks! and Does it need to cinder module to be installed on compute nodes?
Post by Bernd Bausch
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/scheduler-filters.html
.
https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-instance/
Bernd
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
_______________________________________________
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Javier Pena
2018-11-26 09:36:09 UTC
Permalink
----- Original Message -----
Post by Soheil Pourbafrani
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
Post by Soheil Pourbafrani
Post by Bernd Bausch
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/scheduler-filters.html
.
https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-instance/
Bernd
Post by Soheil Pourbafrani
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
_______________________________________________
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Soheil Pourbafrani
2018-11-26 10:07:31 UTC
Permalink
Thanks a lot!
------------------------------
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
Post by Bernd Bausch
Yes. You need to enable Cinder’s InstanceLocalityFilter, see
https://docs.openstack.org/cinder/latest/configuration/block-storage/scheduler-filters.html
.
https://ask.openstack.org/en/question/92001/cinder-lvm-volume-local-to-instance/
Bernd
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
_______________________________________________
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Chhavi Agarwal
2018-11-27 12:52:10 UTC
Permalink
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
iain MacDonnell
2018-11-27 18:52:48 UTC
Permalink
Post by Chhavi Agarwal
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-constraints.txt

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : ***@lists.openstack.org
Unsubscribe : http:
Sean McGinnis
2018-11-27 19:08:58 UTC
Permalink
Post by iain MacDonnell
Post by Chhavi Agarwal
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
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
Chhavi Agarwal
2018-11-28 04:42:33 UTC
Permalink
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.txt
oslo.messaging===9.2.1

[***@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-constraints.txt
} {opts} {packages}
[***@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 <***@gmail.com>
To: ***@oracle.com
Cc: ***@in.ibm.com, ***@lists.openstack.org,
openstack-***@lists.openstack.org,
***@electronicjungle.net, John Griffith
<***@gmail.com>
Date: 11/28/2018 12:39 AM
Subject: Re: [Openstack] [Cinder] Cinder New Tag Release
Post by iain MacDonnell
Post by Chhavi Agarwal
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,
Post by iain MacDonnell
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

Loading...