Skip to content
Snippets Groups Projects
Select Git revision
  • deployment default
1 result
Search by author
  • Any Author
  • KANAPA SYLVERE p1919734 KANAPA SYLVERE p1919734 p1919734
1 author
  1. Oct 10, 2016
  3. Oct 09, 2016
  5. Oct 03, 2016
  7. Sep 29, 2016
    • Jeffrey Zhang's avatar
      Integrate gnocchi with ceph · 96318fed
      Jeffrey Zhang authored 
      Gnocchi previously lacked high availability. We consider a lack of HA
in our a vast majority of operator oriented services to be a defective
design choice. this change integrates gnocchi with ceph to resolve the
the lack of HA.

Closes-Bug: #1626623
Change-Id: I71c5137842cb48bc4af0e50a2952df5631d0d6df
      96318fed
  9. Sep 26, 2016
    • Sajauddin Mohammad's avatar
      Changed docker_restart_policy to unless-stopped · 3f134d0f
      Sajauddin Mohammad authored 
      Current implementation has docker_restart_policy "always" and
docker_restart_policy_retry:"10" which should be mutually exclusive.
"unless-stopped" will restart the containers on any exit state
but not start on daemon startup if container was put to stopped state before.
Closes-Bug: #1621187

Change-Id: I4d881cd123a55625121b7a9047385e9b54e2e129
      3f134d0f
  11. Sep 25, 2016
  13. Sep 22, 2016
  15. Sep 21, 2016
    • Vladislav Belogrudov's avatar
      Cinder cannot use external non-LVM iSCSI storage · b1f986c3
      Vladislav Belogrudov authored 
      Currently Cinder enables iscsid service only when LVM is choosen as
backend. This fix will allow to specify external iSCSI storage via
configuration add-on and to run iscsid independently of LVM settings.

Change-Id: Iaae0f8025534e5ab1c5f9d5e812a7d41129915ef
Closes-Bug: 1614125
      b1f986c3
  17. Sep 16, 2016
  19. Sep 15, 2016
  21. Sep 14, 2016
  23. Sep 13, 2016
  25. Sep 12, 2016
  27. Sep 09, 2016
    • prithiv's avatar
      Ansible roles for collectd Container · 4af9bbe2
      prithiv authored 
      Collectd-ceilometer-plugin is essential for further
more detailed metrics collection, smarter scheduling and service
assurance.

Change-Id: I8da572980de370517ec120d745ad1d36e316b465
Implements: blueprint collectd-ceilometer-plugin
      4af9bbe2
  29. Sep 08, 2016
  31. Sep 07, 2016
  33. Sep 06, 2016
    • zhubingbing's avatar
      Add gnocchi ansible role · 89392f4f
      zhubingbing authored 
      Partially-Implements: blueprint ansible-gnocchi

Change-Id: I8dd0460bd21ac0a233fab0142ec7b6079459bdc2
      89392f4f
  35. Sep 02, 2016
    • Mathias Ewald's avatar
      Added influxdb role · 49f7359b
      Mathias Ewald authored 
      
Added ansible role for influxdb

Introduced host groups for monitoring and influxdb and assign role

Monitoring is deployed on a separate node called monitoring01 by
default

Co-Authored-By: default avatarzhubingbing <zhubingbing10@gmail.com>

Change-Id: If2465a14b18c6c3fd657af587a0b85f6b7a0191a
Partially-Implements: Blueprint performance-monitoring
      49f7359b
  37. Sep 01, 2016
  39. Aug 31, 2016
    • Sean Mooney's avatar
      generate bifrost yaml configs · d7dfae75
      Sean Mooney authored 
      - This change indroduces a merge_yaml action_plugin
- This change generates bifrost yaml configs.

Change-Id: I9814e6a5d55cbd46c4b60c06ed70ed54a575bd2f
Implements: blueprint bifrost-support
      d7dfae75
    • liyingjun's avatar
      Add option to support dhcp/l3 agent ha · c5668bd5
      liyingjun authored 
      New option enable_neutron_agent_ha added to enable/disable dhcp/l3 agent
high availability, dhcp_agents_per_network is default to 2 and it's
configurable.

Implement blueprint: support-network-ha

Change-Id: Id4742aa67c80584634b923195545bf2b654172f3
      c5668bd5
    • zhubingbing's avatar
      Add aodh role · 7ce05f97
      zhubingbing authored 
      Partially-Implements: blueprint ansible-aodh

Change-Id: I9e20f4bf5e7d8f37f243ae15746e2b7bb49eb20c
      7ce05f97
  41. Aug 29, 2016
    • Paul Bourke's avatar
      Add a check before wiping Ceph disks in bootstrap · ec40ed3c
      Paul Bourke authored 
      An unwitting user may apply the KOLLA_CEPH_OSD[_CACHE]_BOOTSTRAP label
to a partition assuming it will only use that partition for Ceph, and
end up wiping out their disk.

This change adds a layer of checking to this scenario to try and help
avoid a disaster scenario.

Closes-Bug: 1599103
DocImpact

Change-Id: Ibb9fb42f87a76bc02165ec0b93b60234bad8747a
      ec40ed3c
  43. Aug 25, 2016
    • Shaun Smekel's avatar
      Add full support for fernet · 1c68ae38
      Shaun Smekel authored 
      This addresses the ansible aspects of fernet key bootstrapping as
well as distributed key rotation.

- Bootstrapping is handled in the same way as keystone bootstrap.
- A new keystone-fernet and keystone-ssh container is created to allow
  the nodes to communicate with each other (taken from nova-ssh).
- The keystone-fernet is a keystone container with crontab installed.
  This will handle key rotations through keystone-manage and trigger
  an rsync to push new tokens to other nodes.
- Key rotation is setup to be balanced across the keystone nodes using
  a round-robbin style. This ensures that any node failures will not
  stop the keys from rotating. This is configured by a desired token
  expiration time which then determines the cron scheduling for each
  node as well as the number of fernet tokens in rotation.
- Ability for recovered node to resync with the cluster. When a node
  starts it will run sanity checks to ensure that its fernet tokens
  are not stale. If they are it will rsync with other nodes to ensure
  its tokens are up to date.

The Docker component is implemented in:
  https://review.openstack.org/#/c/349366

Change-Id: I15052c25a1d1149d364236f10ced2e2346119738
Implements: blueprint keystone-fernet-token
      1c68ae38
  45. Aug 24, 2016
    • Paul Bourke's avatar
      Add defaults for interfaces to all.yml · 158a8529
      Paul Bourke authored 
      The values for 'network_interface' and 'neutron_external_interface' are
missing from all.yml, meaning it is impossible to override them on a per
node / per group basis. (globals.yml get's top precedence).

Make these consistent with the rest of the variables and move the
defaults into all.yml. Operators can still override / update these in
globals.yml as before, but those wanting more flexibility now have it
via host / group variables.

Change-Id: I2575921f76a8e245106da765757c70353bd6762c
Closes-Bug: #1604129
      158a8529
  47. Aug 17, 2016
  49. Aug 10, 2016
    • Ken Wronkiewicz's avatar
      Fix intf address for RabbitMQ and disable cluster for Kube · cc415029
      Ken Wronkiewicz authored 
      
enable_rabbitmq_cluster is now a "yes" by default but you can set it
to "no" if you want to disable clustering under any circumstances.

The agreement made at OpenStack in Austin was that Kolla-Kubernetes
would concentrate on RabbitMQ and MariaDB without clustering but
with persistent storage and workload migration, then examine how to
do proper distributed functionality as the project progresses, so I
am just following what we'd already agreed upon.

First, it helps us deal with issues of version upgrades without
dealing with clustered version upgrades and the synchronization
thereof.

Second, it provides an alternative model for durability when used in
Kubernetes.  Understand that, if we disable RabbitMQ's clustering,
Kubernetes is still able to re-schedule the queue off of a failed node
in ways that Kolla-Ansible is not.  There are known issues with
RabbitMQ clustering, especially with auto-heal turned on.  For many
small-to-mid-sized clusters, it's going to provide for a better
operator experience to have the known potential for a 30 second blip
after RabbitMQ node failure than it is to have the known potential
for partition and data loss and/or manual operations after you've
turned off auto-heal.

Kolla-kubernetes has already turned off host networking for the
RabbitMQ pod; it's safe to set the interface address in the
Kubernetes context.

The question was asked why don't I just set the RabbitMQ cluster to be
a single instance.  It's unlikely that Kubernetes RabbitMQ with a
PetSet will be clustered in the same declaritive fashion as the
rabbitmq-clusterer plugin. Easier to just disable it and worry about
how to configure the kube-friendly clustered RabbitMQ at a later point
in time.  Furthermore, it's an entirely valid case for many OpenStack
control planes hosted atop Kolla-Kubernetes to accept the possibility
of a 30-60 second blip in lieu of the long and questionable history
of RabbitMQ clustering in production.

Co-authored-by: default avatarRyan Hallisey <rhallise@redhat.com>
Change-Id: I7f0cb22d29a418fce4af8d69f63739859173d746
Partially-implements: blueprint api-interface-bind-address-override
      cc415029