Hippie Hacker

### Prometheus Releases No CI releases as of yet There is a [reproducible load/performance test](https://github.com/prometheus/prombench), but binaries are released manually. tarballs: https://github.com/prometheus/prometheus/releases/ containers: https://quay.io/repository/prometheus/prometheus?tab=tags The [Solicitation of CI requirements conversation](https://github.com/prometheus/prometheus/issues/2497)...

### Fluentd No CI releases as of yet CI test occur building the gem: https://travis-ci.org/fluent/fluentd/ Tarballs: https://github.com/fluent/fluentd-docker-image/releases Gems: https://rubygems.org/gems/fluentd/versions

https://help.packet.net/technical#api-automation https://help.packet.net/technical/infrastructure/deploying-a-container-linux-coreos-cluster https://help.packet.net/technical/infrastructure/custom-ipxe

Similar lines: https://www.packet.net/developers/guides/mesos-dcos-with-terraform/ https://www.terraform.io/docs/providers/packet/r/device.html#user_data

@zilman can I grab some creds / an account for Packet?

Currently takes about 4.5-6.5 minutes to deploy. DNS is an issue currently. And we have a request to integrate CoreDNS cncf/demo#190

https://github.com/lynx44/windows_ssl#bind_certificate ? ``` ruby windows_ssl_bind_certificate "bind the ssl cert" do hash '991deaa340c14b45214927f58a8b7288d9ce6906' port 443 ip_address '0.0.0.0' app_guid '1A25F4DE-A3DE-FEA2-EAF0-023FA1AD324' action :bind end ``` In https://github.com/lynx44/windows_ssl/blob/master/providers/bind_certificate.rb#L22 ``` ruby execute "install ssl certificate...

I've actually started using [windows_certificate_binding](https://github.com/chef-cookbooks/windows#windows_certificate_binding) though you have to currently write two resource (one with action :delete with a guard to not delete the desired one, and another with :create)...

``` iis_site 'Default Web Site' do action :config # site_id - if not given IIS generates a unique ID for the site site_id 1 # bindings - Advanced options to...

Let’s drop the existing CI wg, and we’ll relaunch the ongoing initiatives under #tag-contributor-strategy and a new Contributor Infrastructure WG