Re: [rdo-users] Creating CRUSH placement rules with TripleO

2018-10-15 Thread John Fulton 
On Sat, Oct 13, 2018 at 4:04 PM Cody  wrote:
>
> Hello John,
>
> Thank you for pointing me to the right direction. I wish I could be
> more knowledgeable in using ceph-ansible for making customization at
> the deployment time.
>
> After going through the docs, I came up with the following environment
> file in hope to assign SSD to the "vms" pool and HDD to the "volumes"
> pool using TripleO.
>
> parameter_defaults:
> CephAnsibleExtraConfig:
>crush_rule_config: true

so far so good but I don't know about the following:

>crush_rule_hdd:
>   name: replicated_hdd
>   root: default
>   type: host
>   device_class: hdd
>   default: false
>crush_rule_ssd:
>   name: replicated_ssd
>   root: default
>   type: host
>   device_class: ssd
>   default: false

Try something more like this. Also, I assume you want one to be the
default so that if create a pool it ends up in one of the two
crush_rules.

crush_rules:
  - name: replicated_hdd
root: standard_root
type: host
default: true
  - name: replicated_ssd
root: fast_root
type: host
default: false

>crush_rules:
>   - "{{ crush_rule_hdd }}"
>   - "{{ crush_rule_ssd }}"

The environment file is THT, not ansible. I don't think this will work
and you should just be bale to omit the 3 lines above.

>create_crush_tree: true

Good.

>   CephPools:
>   - name: vms
> rule_name: replicated_ssd
>   - name: volumes
> rule_name: replicated_hdd

Yes. You could also add pg_num to the above per pool.

Also, watch out for https://bugzilla.redhat.com/show_bug.cgi?id=1638092

  John

>
> Thank you very much and have a good weekend!
>
> Best regards,
> Cody
> On Sat, Oct 13, 2018 at 3:33 AM John Fulton  wrote:
> >
> > On Saturday, October 13, 2018, Cody  wrote:
> >>
> >> Hi everyone,
> >>
> >> Is it possible to define CRUSH placement rules and apply to different
> >> pools while using TripleO to deploy an overcloud with Ceph
> >> integration?
> >>
> >> I wish to set the "vms" pool to use SSDs and "volumes" pool to use
> >> HDDs. On a pre-existing Ceph cluster, I can define CRUSH placement
> >> rules using device-class and apply the corresponding rules when create
> >> pools. But, I don't know how to do so with TripleO.
> >>
> >> Could someone shed light on this?
> >
> >
> > CRUSH rules may be passed to specific nodes. You may identify specific 
> > nodes in TripleO by using node-specific overrides as per:
> >
> > https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/node_specific_hieradata.html
> >
> > In the documentation above a specific devices list is passed to a specific 
> > node. However, you may pass other properties to the specific node including 
> > the osd_crush_location. For example:
> >
> > {"32C2BC31-F6BB-49AA-971A-377EFDFDB111": {"osd_crush_location": {"root": 
> > "standard_root", "rack": "rack1_std", "host": "lab-ceph01"}},
> >
> > TripleO then will map the node's UUID to the IP used in the ceph-ansible 
> > inventory and pass node specific variable overrides.
> >
> > You'll also want to use CephAnsibleExtraConfig to override specific 
> > ceph-ansible variables for all nodes, e.g.
> >
> >   CephAnsibleExtraConfig:
> > create_crush_tree: true
> >
> > More info at 
> > https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/ceph_config.html
> >
> > Overall, if you know how to make ceph-ansible do what you need it to do, 
> > then TripleO can pass the variables to ceph-ansible to achieve it.
> >
> >   John
> >
> >>
> >>
> >> Best regards,
> >> Cody
> >> ___
> >> users mailing list
> >> users@lists.rdoproject.org
> >> http://lists.rdoproject.org/mailman/listinfo/users
> >>
> >> To unsubscribe: users-unsubscr...@lists.rdoproject.org
___
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org

Re: [rdo-users] [tripleo][cinder][horizon]Unable to use Cinder volume as _member_ or member in Horizon

2018-10-15 Thread Tobias Urdin 

Hello,

Might not be related but when we upgraded from Queens to Rocky the 
Cinder API stopped
working when requests with query parameters in the URL were passed, the 
API just responded

with 400 bad request, but without query parameters the request worked.

We ended up having to add the resource_filters.json file to /etc/cinder 
directory which was not

in the cinder RDO package, have a patch up for that [1].

We fixed it manually in our upgrade workflow with Ansible.

- name: check cinder resource_filters.json file
  stat: path=/etc/cinder/resource_filters.json
  register: resource_filters_file

- name: download cinder resource_filters.json if not exist
  get_url:
    url: 
"https://git.openstack.org/cgit/openstack/cinder/plain/etc/cinder/resource_filters.json?h=stable/{{ 
openstack_version | lower }}"

    dest: /etc/cinder/resource_filters.json
    owner: root
    group: cinder
    mode: 0644
  when: not resource_filters_file.stat.exists

Best regards
Tobias

[1] https://review.rdoproject.org/r/#/c/16448/

On 10/15/2018 02:31 PM, Tzach Shefi wrote:

Hey Cody,

Sorry for delay, just getting back up to speed.
I just checked on my Rocky (OPSD) deployment same issue with 
Cinder/Horizon.

In my case I created a new project/user (as _member_)
Creating an empty volume fails with same errors you reported:
Error: Unable to retrieve volumes
Error: Unable to retrieve volume snapshots

Checking with folks here, I'll get back to you with an answer.

Tzach


On Fri, Oct 12, 2018 at 2:57 AM Cody > wrote:


Hello everyone,

Lately I run into two problems with using TripleO to deploy
OpenStack (Queens). One of them is that users with _member_ or
member roles appear to be unable to use cinder-volume service via
the Dashboard (Horizon).

For any projects, users with either _member_ or member role
received following pop-up error messages while trying to launch
instances:

Error: Unable to retrieve volumes
Error: Unable to retrieve volume snapshots

There is also no volume option to choose from the drop-down menu
in the Source sector, although the bootable volume is present and
publicly accessible.

It doesn't affect the same users using CLI - they can create
volumes or boot instances from volume normally from the command line.

The issue is reproducible and consistent with varied cluster
configurations and cinder backends (nfs, file, rbd).

Has anyone else encountered the same experience?


Best regards,
Cody










___
users mailing list
users@lists.rdoproject.org 
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org




--

Tzach Shefi

Senior Quality Engineer, RHCSA

Red Hat



tsh...@redaht.com  M: +972-54-4701080 
 IM: tshefi






___
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org

[rdo-users] [Fedocal] Reminder meeting : RDO meeting

2018-10-15 Thread hguemar 
Dear all,

You are kindly invited to the meeting:
   RDO meeting on 2018-10-17 from 15:00:00 to 16:00:00 UTC
   At r...@irc.freenode.net

The meeting will be about:
RDO IRC meeting
[Agenda at https://etherpad.openstack.org/p/RDO-Meeting 
](https://etherpad.openstack.org/p/RDO-Meeting)

Every Wednesday on #rdo on Freenode IRC


Source: https://apps.fedoraproject.org/calendar/meeting/8759/

___
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org

[rdo-users] [Fedocal] Reminder meeting : RDO Office Hours

2018-10-15 Thread chkumar246 
Dear all,

You are kindly invited to the meeting:
   RDO Office Hours on 2018-10-16 from 13:30:00 to 14:30:00 UTC
   

The meeting will be about:
The meeting will be about RDO Office Hour.

Aim: To keep up with increasing participation, we'll host office hours to add 
more easy fixes and provide mentoring to newcomers.


[Agenda at RDO Office Hour 
easyfixes](https://review.rdoproject.org/etherpad/p/rdo-office-hour-easyfixes)



Source: https://apps.fedoraproject.org/calendar/meeting/6374/

___
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org

Re: [rdo-users] [tripleo][cinder][horizon]Unable to use Cinder volume as _member_ or member in Horizon

2018-10-15 Thread Tzach Shefi 
Hey Cody,

Sorry for delay, just getting back up to speed.
I just checked on my Rocky (OPSD) deployment same issue with
Cinder/Horizon.
In my case I created a new project/user (as _member_)
Creating an empty volume fails with same errors you reported:
Error: Unable to retrieve volumes
Error: Unable to retrieve volume snapshots

Checking with folks here, I'll get back to you with an answer.

Tzach


On Fri, Oct 12, 2018 at 2:57 AM Cody  wrote:

> Hello everyone,
>
> Lately I run into two problems with using TripleO to deploy OpenStack
> (Queens). One of them is that users with _member_ or member roles appear to
> be unable to use cinder-volume service via the Dashboard (Horizon).
>
> For any projects, users with either _member_ or member role received
> following pop-up error messages while trying to launch instances:
>
> Error: Unable to retrieve volumes
> Error: Unable to retrieve volume snapshots
>
> There is also no volume option to choose from the drop-down menu in the
> Source sector, although the bootable volume is present and publicly
> accessible.
>
> It doesn't affect the same users using CLI - they can create volumes or
> boot instances from volume normally from the command line.
>
> The issue is reproducible and consistent with varied cluster
> configurations and cinder backends (nfs, file, rbd).
>
> Has anyone else encountered the same experience?
>
>
> Best regards,
> Cody
>
>
>
>
>
>
>
>
>
>
> ___
> users mailing list
> users@lists.rdoproject.org
> http://lists.rdoproject.org/mailman/listinfo/users
>
> To unsubscribe: users-unsubscr...@lists.rdoproject.org
>


-- 

Tzach Shefi

Senior Quality Engineer, RHCSA

Red Hat



tsh...@redaht.comM: +972-54-4701080 IM: tshefi

___
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscr...@lists.rdoproject.org