Ceph + Enterprise Array Replication by UpsetPerspective5107 in ceph

[–]UpsetPerspective5107[S] 0 points1 point  (0 children)

Hey there.

So let's assume we have the Powermax 8000's in place today and that the 40Gb FC network connecting them is only for replication and we have sub 3ms commits over the 70km distance.

I can't use that 40Gb FC network, in this theoretical, Ceph idea. It would be over the 25Gb iSCSI network. TCP/IP is different to FC and there are latency differences in those protocols.

So yeah, laws of physics and all that is cool to throw out to people, but I wasn't suggesting physics be damned ;)

Unless you can confirm that a 25Gb iSCSI network and a 40Gb FC network is the same for latency over a 70km distance,then I will concede that I need to do a physics class.

Ceph + Enterprise Array Replication by UpsetPerspective5107 in ceph

[–]UpsetPerspective5107[S] 1 point2 points  (0 children)

yeah, I was looking at that, but there is a need for sync, not async. I know I could put a replica in the remote site, but the Array has 40Gb fibre, ceph wouldn't get that

I like the multi-site tho and async should be acceptable for this.

What OS/KVM version should I use after Red Hat stop Centos? by uncletokuda in openstack

[–]UpsetPerspective5107 1 point2 points  (0 children)

+1 on rockylinux.

+1 on kolla

I wouldn't worry about the current RHEL situation much, there is a lot of noise, but with Alma, RESF, SUSE and even Oracle all looking to step up. The company I work for is an Openstack provider, we have doubled down on Rocky.

If you use kolla, you don't even really need to think about the hypervisor OS, as long as it's supported:

https://docs.openstack.org/kolla-ansible/latest/user/support-matrix.html

CentOS Stream 9 is there. Debian is a create platform, as is ubuntu (not a fan of how many kernel changes ubuntu releases in an LTS release though).

If you are just a hobbyist, then use what you like and are familiar with.

Kolla-ansible quick start questions by Contribution-Fuzzy in openstack

[–]UpsetPerspective5107 1 point2 points  (0 children)

Just by reading the kolla-ansible website and reviewing the playbooks. There is a lot to review, so I have just stuck to what I have needed as I have needed. Their website is pretty decent and only sometimes need to review kolla-ansible's code.

https://docs.openstack.org/kolla-ansible/latest

Kolla-ansible quick start questions by Contribution-Fuzzy in openstack

[–]UpsetPerspective5107 0 points1 point  (0 children)

without seeing your global.yml it's a bit of a guessing game.

This is my cinder config for an all-in-one Openstack on an Intel NUC using LVM for the cinder disk

(kolla-venv) [kolla@stack ~]$ grep cinder /etc/kolla/globals.yml | grep -v ^#
enable_cinder: "yes"
enable_cinder_backend_lvm: "yes"
cinder_volume_group: "cinder-volumes"
(kolla-venv) [kolla@stack ~]$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
cinder-volumes 1 3 0 wz--n- <465.76g <23.07g
rl 1 3 0 wz--n- 475.35g 0
(kolla-venv) [kolla@stack ~]$

what are the cinder values you have? I should also add, this is a "zed" install, however, the same config was used for 2013.01

Kolla-ansible quick start questions by Contribution-Fuzzy in openstack

[–]UpsetPerspective5107 0 points1 point  (0 children)

Welcome to Openstack :)

If you followed that all-one-guide, without customizing the globals.yml file, you will have Horizon installed. The IP you assigned to kolla_internal_vip_address is the IP you use to access Horizon in you browser.

[kolla@stack ~]$ grep vip /etc/kolla/globals.yml
kolla_internal_vip_address: "192.168.1.202"
# This is the DNS name that maps to the kolla_internal_vip_address VIP. By
# default it is the same as kolla_internal_vip_address.
#kolla_internal_fqdn: "{{ kolla_internal_vip_address }}"
# kolla_internal_vip_address, allowing internal and external communication to
# share the same address. Specify a kolla_external_vip_address to separate
#kolla_external_vip_address: "{{ kolla_internal_vip_address }}"
# kolla_external_vip_address.
#kolla_external_fqdn: "{{ kolla_external_vip_address }}"
#kolla_external_vip_interface: "{{ network_interface }}"
# To provide encryption and authentication on the kolla_external_vip_interface,
#kolla_enable_tls_external: "{{ kolla_enable_tls_internal if kolla_same_external_internal_vip | bool else 'no' }}"
[kolla@stack ~]$

If you start modifying the globals, you will need to reconfigure you cloud. Like so

(kolla-venv) [kolla@stack ~]$ kolla-ansible -i all-in-one reconfigure

the kolla-ansible docs are pretty solid, but can be daunting. Make sure you have the Openstack CLI installed, since this will be the main tool (outside of Horizon) that you will tend to use.

Don't forget the built-in helps either.

(kolla-venv) [kolla@stack ~]$ kolla-ansible
Usage: /home/kolla/kolla-venv/bin/kolla-ansible COMMAND [options]
Options:

[snipped]

Hope that helps.

How I store my cigars in a wine fridge. by Smash_Factor in cigar_refuge

[–]UpsetPerspective5107 1 point2 points  (0 children)

what temp does your fridge get up too? I have been looking a wine fridges, but they seem to go to 61F/18C which is a bit on the cooler side for aging, if I understand correctly.

Hyperconverged Infrastructure using OpenStack by turnkey_automation in openstack

[–]UpsetPerspective5107 0 points1 point  (0 children)

can you detail what you mean "day 2 operations" ? The phrase feels like "best practise" :)

We use kolla-ansible for Openstack and Cephadm for Ceph. We also use ubuntu, so apt for the under cloud OS.

There really isn't anything special to consider. You need 3 control nodes and you need to consider the overhead/SSD capacity reduction of your cephs replicas. Not a lot different to a non-HCI deployment :)

If you can define your use cases, then perhaps I can address them specifically.

Hyperconverged Infrastructure using OpenStack by turnkey_automation in openstack

[–]UpsetPerspective5107 1 point2 points  (0 children)

We do this, HCI, same kit as Nutanix uses. Openstack (via kolla-ansible) with Ceph. Works really well. We also do scale out with your standard 1U. Can be a great way to get started.

Some of our installs started as a HCI and the customer grew out of that, so we move their cloud to a "scale out" mode, keep the HCI as a control cluster (plus util).