Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels
What about Rocket chat instead of Slack? It is open source. https://github.com/RocketChat/Rocket.Chat Monty, what kind of evaluation would you guys need? I might be able to help. On Wed, Aug 1, 2018 at 9:54 AM, Monty Taylor wrote: > On 08/01/2018 07:44 AM, Doug Hellmann wrote: > >> Excerpts from Andrey Kurilin's message of 2018-08-01 15:21:37 +0300: >> >>> ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur : >>> >>> On 08/01/2018 12:49 PM, Andrey Kurilin wrote: >>>> >>>>> Hey Ian and stackers! >>>>> >>>>> ср, 1 авг. 2018 г. в 8:45, Ian Wienand >>>> <mailto:iwien...@redhat.com>>: >>>>> >>>>> Hello, >>>>> >>>>> It seems freenode is currently receiving a lot of unsolicited >>>>> traffic >>>>> across all channels. The freenode team are aware [1] and doing >>>>> their >>>>> best. >>>>> >>>>> There are not really a lot of options. We can set "+r" on >>>>> channels >>>>> which means only nickserv registered users can join channels. We >>>>> >>>> have >>>> >>>>> traditionally avoided this, because it is yet one more barrier to >>>>> communication when many are already unfamiliar with IRC access. >>>>> However, having channels filled with irrelevant messages is also >>>>> not >>>>> very accessible. >>>>> >>>>> This is temporarily enabled in #openstack-infra for the time >>>>> being, >>>>> >>>> so >>>> >>>>> we can co-ordinate without interruption. >>>>> >>>>> Thankfully AFAIK we have not needed an abuse policy on this >>>>> before; >>>>> but I guess we are the point we need some sort of coordinated >>>>> response. >>>>> >>>>> I'd suggest to start, people with an interest in a channel can >>>>> >>>> request >>>> >>>>> +r from an IRC admin in #openstack-infra and we track it at [2] >>>>> >>>>> Longer term ... suggestions welcome? :) >>>>> >>>>> >>>>> Move to Slack? We can provide auto-sending to emails invitations for >>>>> >>>> joining by >>>> >>>>> clicking the button on some page at openstack.org < >>>>> http://openstack.org>. >>>>> >>>> It >>>> >>>>> will not add more berrier for new contributors and, at the same time, >>>>> >>>> this way >>>> >>>>> will give some base filtering by emails at least. >>>>> >>>> >>>> A few potential barriers with slack or similar solutions: lack of FOSS >>>> desktop >>>> clients (correct me if I'm wrong), >>>> >>> >>> >>> The second link from google search gives an opensource client written in >>> python https://github.com/raelgc/scudcloud . Also, there is something >>> which >>> is written in golang. >>> >>> complete lack of any console clients (ditto), >>>> >>>> >>> Again, google gives several ones as first results - >>> https://github.com/evanyeung/terminal-slack >>> https://github.com/erroneousboat/slack-term >>> >>> serious limits on free (as in beer) tariff plans. >>> >>>> >>>> >>>> I can make an assumption that for marketing reasons, Slack Inc can >>> propose >>> extended Free plan. >>> But anyway, even with default one the only thing which can limit us is >>> `10,000 searchable messages` which is bigger than 0 (freenode doesn't >>> store >>> messages). >>> >>> >>> Why I like slack? because a lot of people are familar with it (a lot of >>> companies use it as like some opensource communities, like k8s ) >>> >>> PS: I realize that OpenStack Community will never go away from Freenode >>> and >>> IRC, but I do not want to stay silent. >>> >> >> We are unlikely to select slack because the platform itself is >> proprietary, even if there are OSS clients. That said, there have >> been some discussions about platforms such as Matrix, which is >> similar to slack and also OSS. >> >> I think the main thing that is blocking any such move right now is >> the fact that we're lacking someone with time to evaluate the tool >> to see what it would take for us to run it. If you're interested in >> this, maybe you can work with the infrastructure team to plan and >> implement that evaluation? >> > > In Vancouver I signed up to work on this - but so far it has been lower in > priority than other tasks. I'll circle around with people today and see > what we think about relative priorities. > > That said - Doug's invitation is quite valid - help would be welcome and > I'd be happy to connect with someone who has time to help with this. > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Rafael Weingärtner __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Problem when deploying Openstack with Kolla
ent. > > # Glance > [glance-api:children] > glance > > [glance-registry:children] > glance > > # Nova > [nova-api:children] > nova > > [nova-conductor:children] > nova > > [nova-consoleauth:children] > nova > > [nova-novncproxy:children] > nova > > [nova-scheduler:children] > nova > > [nova-spicehtml5proxy:children] > nova > > [nova-compute-ironic:children] > nova > > [nova-serialproxy:children] > nova > > # Neutron > [neutron-server:children] > control > > [neutron-dhcp-agent:children] > neutron > > [neutron-l3-agent:children] > neutron > > [neutron-lbaas-agent:children] > neutron > > [neutron-metadata-agent:children] > neutron > > [neutron-bgp-dragent:children] > neutron > > [neutron-infoblox-ipam-agent:children] > neutron > > # Ceph > [ceph-mds:children] > ceph > > [ceph-mgr:children] > ceph > > [ceph-nfs:children] > ceph > > [ceph-mon:children] > ceph > > [ceph-rgw:children] > ceph > > [ceph-osd:children] > storage > > # Cinder > [cinder-api:children] > cinder > > [cinder-backup:children] > storage > > [cinder-scheduler:children] > cinder > > [cinder-volume:children] > storage > > # Cloudkitty > [cloudkitty-api:children] > cloudkitty > > [cloudkitty-processor:children] > cloudkitty > > # Freezer > [freezer-api:children] > freezer > > [freezer-scheduler:children] > freezer > > # iSCSI > [iscsid:children] > compute > storage > ironic > > [tgtd:children] > storage > > # Karbor > [karbor-api:children] > karbor > > [karbor-protection:children] > karbor > > [karbor-operationengine:children] > karbor > > # Manila > [manila-api:children] > manila > > [manila-scheduler:children] > manila > > [manila-share:children] > network > > [manila-data:children] > manila > > # Swift > [swift-proxy-server:children] > swift > > [swift-account-server:children] > storage > > [swift-container-server:children] > storage > > [swift-object-server:children] > storage > > # Barbican > [barbican-api:children] > barbican > > [barbican-keystone-listener:children] > barbican > > [barbican-worker:children] > barbican > > # Trove > [trove-api:children] > trove > > [trove-conductor:children] > trove > > [trove-taskmanager:children] > trove > > # Heat > [heat-api:children] > heat > > [heat-api-cfn:children] > heat > > [heat-engine:children] > heat > > # Murano > [murano-api:children] > murano > > [murano-engine:children] > murano > > # Ironic > [ironic-api:children] > ironic > > [ironic-conductor:children] > ironic > > [ironic-inspector:children] > ironic > > [ironic-pxe:children] > ironic > > # Magnum > [magnum-api:children] > magnum > > [magnum-conductor:children] > magnum > > # Solum > [solum-api:children] > solum > > [solum-worker:children] > solum > > [solum-deployer:children] > solum > > [solum-conductor:children] > solum > > # Mistral > [mistral-api:children] > mistral > > [mistral-executor:children] > mistral > > [mistral-engine:children] > mistral > > # Aodh > [aodh-api:children] > aodh > > [aodh-evaluator:children] > aodh > > [aodh-listener:children] > aodh > > [aodh-notifier:children] > aodh > > # Panko > [panko-api:children] > panko > > # Gnocchi > [gnocchi-api:children] > gnocchi > > [gnocchi-statsd:children] > gnocchi > > [gnocchi-metricd:children] > gnocchi > > # Sahara > [sahara-api:children] > sahara > > [sahara-engine:children] > sahara > > # Ceilometer > [ceilometer-central:children] > ceilometer > > [ceilometer-notification:children] > ceilometer > > [ceilometer-compute:children] > compute > > # Congress > [congress-api:children] > congress > > [congress-datasource:children] > congress > > [congress-policy-engine:children] > congress > > # Multipathd > [multipathd:children] > compute > > # Watcher > [watcher-api:children] > watcher > > [watcher-engine:children] > watcher > > [watcher-applier:children] > watcher > > # Senlin > [senlin-api:children] > senlin > > [senlin-engine:children] > senlin > > # Searchlight > [searchlight-api:children] > searchlight > > [searchlight-listener:children] > searchlight > > # Octavia > [octavia-api:children] > octavia > > [octavia-health-manager:children] > octavia &g
Re: [openstack-dev] Problem when deploying Openstack with Kolla
cchi_backend_storage: "{{ 'ceph' if enable_ceph|bool else 'file' }}"
>
> # Valid options are [redis, '']
> #gnocchi_incoming_storage: "{{ 'redis' if enable_redis | bool else '' }}"
>
>
> # Cinder - Block Storage Options
>
> # Enable / disable Cinder backends
> #cinder_backend_ceph: "{{ enable_ceph }}"
> #cinder_backend_vmwarevc_vmdk: "no"
> #cinder_volume_group: "cinder-volumes"
>
> # Valid options are [ nfs, swift, ceph ]
> #cinder_backup_driver: "ceph"
> #cinder_backup_share: ""
> #cinder_backup_mount_options_nfs: ""
>
>
> ###
> # Designate options
> ###
> # Valid options are [ bind9 ]
> #designate_backend: "bind9"
> #designate_ns_record: "sample.openstack.org"
>
>
> # Nova - Compute Options
>
> #nova_backend_ceph: "{{ enable_ceph }}"
>
> # Valid options are [ qemu, kvm, vmware, xenapi ]
> #nova_compute_virt_type: "kvm"
>
> # The number of fake driver per compute node
> #num_nova_fake_per_node: 5
>
> #
> # Hyper-V options
> #
> # Hyper-V can be used as hypervisor
> #hyperv_username: "user"
> #hyperv_password: "password"
> #vswitch_name: "vswitch"
> # URL from which Nova Hyper-V MSI is downloaded
> #nova_msi_url: "
> https://www.cloudbase.it/downloads/HyperVNovaCompute_Beta.msi";
>
> #########
> # Horizon - Dashboard Options
> #
> #horizon_backend_database: "{{ enable_murano | bool }}"
>
> #
> # Ironic options
> #
> # following value must be set when enable ironic, the value format
> # is "192.168.0.10,192.168.0.100".
> ironic_dnsmasq_dhcp_range:
>
> ##
> # Manila - Shared File Systems Options
> ##
> # HNAS backend configuration
> #hnas_ip:
> #hnas_user:
> #hnas_password:
> #hnas_evs_id:
> #hnas_evs_ip:
> #hnas_file_system_name:
>
>
> # Swift - Object Storage Options
>
> # Swift expects block devices to be available for storage. Two types of
> storage
> # are supported: 1 - storage device with a special partition name and
> filesystem
> # label, 2 - unpartitioned disk with a filesystem. The label of this
> filesystem
> # is used to detect the disk which Swift will be using.
>
> # Swift support two matching modes, valid options are [ prefix, strict ]
> #swift_devices_match_mode: "strict"
>
> # This parameter defines matching pattern: if "strict" mode was selected,
> # for swift_devices_match_mode then swift_device_name should specify the
> name of
> # the special swift partition for example: "KOLLA_SWIFT_DATA", if "prefix"
> mode was
> # selected then swift_devices_name should specify a pattern which would
> match to
> # filesystems' labels prepared for swift.
> #swift_devices_name: "KOLLA_SWIFT_DATA"
>
>
>
> # Tempest - The OpenStack Integration Test Suite
>
> # following value must be set when enable tempest
> tempest_image_id:
> tempest_flavor_ref_id:
> tempest_public_network_id:
> tempest_floating_network_name:
>
> # tempest_image_alt_id: "{{ tempest_image_id }}"
> # tempest_flavor_ref_alt_id: "{{ tempest_flavor_ref_id }}"
>
> ###
> # VMware - OpenStack VMware support
> ###
> #vmware_vcenter_host_ip:
> #vmware_vcenter_host_username:
> #vmware_vcenter_host_password:
> #vmware_datastore_name:
> #vmware_vcenter_name:
> #vmware_vcenter_cluster_name:
>
> ###
> # XenAPI - Support XenAPI for XenServer
> ###
> # XenAPI driver use HIMN(Host Internal Management Network)
> # to communicate with XenServer host.
> #xenserver_himn_ip:
> #xenserver_username:
> #xenserver_connect_protocol:
>
>
> # Prometheus
>
> #enable_prometheus_haproxy_exporter: "{{ enable_haproxy | bool }}"
> #enable_prometheus_mysqld_exporter: "{{ enable_mariadb | bool }}"
> #enable_prometheus_node_exporter: "yes"
>
On Mon, May 21, 2018 at 10:49 PM, Jeffrey Zh
[openstack-dev] Problem when deploying Openstack with Kolla
Hello OpenStackers,
First of all, I am not sure if this is the right list to post this
question. Therefore, please excuse me if I am sending an e-mail to the
wrong place.
So, I have been trying to use Kolla to deploy a POC environment of
OpenStack. However, I have not been able to do so. Right now I am getting
the following error:
fatal: [localhost]: FAILED! => {"msg": "The conditional check
> '(neutron_l3_agent.enabled | bool and neutron_l3_agent.host_in_groups |
> bool) or (neutron_vpnaas_agent.enabled | bool and
> neutron_vpnaas_agent.host_in_groups | bool)' failed. The error was: error
> while evaluating conditional ((neutron_l3_agent.enabled | bool and
> neutron_l3_agent.host_in_groups | bool) or (neutron_vpnaas_agent.enabled |
> bool and neutron_vpnaas_agent.host_in_groups | bool)): Unable to look up a
> name or access an attribute in template string ({{ inventory_hostname in
> groups['neutron-vpnaas-agent'] }}).\nMake sure your variable name does not
> contain invalid characters like '-': argument of type 'StrictUndefined' is
> not iterable\n\nThe error appears to have been in
> '/usr/local/share/kolla-ansible/ansible/roles/neutron/tasks/config.yml':
> line 2, column 3, but may\nbe elsewhere in the file depending on the exact
> syntax problem.\n\nThe offending line appears to be:\n\n---\n- name:
> Setting sysctl values\n ^ here\n"}
>
It looks like an Ansible problem. I checked the file
“/usr/local/share/kolla-ansible/ansible/roles/neutron/tasks/config.yml” at
line 5, it has the following declaration:
> neutron_l3_agent: "{{ neutron_services['neutron-l3-agent'] }}"
>
As far as I understand everything is ok with this variable declaration.
There is the “neutron-l3-agent” parameter used to retrieve an element from
“neutron_services” map, but that does look ok. Has anybody else experienced
this problem before?
I am using Kolla for OpenStack queens. I am using kolla with the following
command.
> kolla-ansible -i all-in-one bootstrap-servers && kolla-ansible -i
> all-in-one prechecks && kolla-ansible -i all-in-one deploy
>
As you can see, it is a simple use case to deploy OpenStack in a single
node. The command that is failing is the following.
> kolla-ansible -i all-in-one deploy
>
--
Rafael Weingärtner
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
