Thursday, 2020-12-10

*** rezroo has quit IRC03:32
*** dasp has quit IRC05:18
*** evrardjp has quit IRC05:33
*** evrardjp has joined #airshipit05:33
*** dasp has joined #airshipit05:34
*** alexanderhughes has quit IRC06:11
*** francisy has quit IRC06:11
*** alexanderhughes has joined #airshipit06:11
*** mnaser has quit IRC06:11
*** francisy has joined #airshipit06:11
*** mnaser has joined #airshipit06:12
*** evrardjp has quit IRC06:49
*** evrardjp_ has joined #airshipit06:49
*** huyupeng has joined #airshipit07:15
huyupengwhen will airship2.0  be released07:16
huyupengis airship still under develop ?07:27
*** muhaha has joined #airshipit09:03
huyupeng is airship still under develop ?11:23
huyupeng@muhaha11:23
*** huyupeng has quit IRC11:44
*** muhaha has quit IRC13:38
mattmceuen@huyupeng - yes, still under development.  We're targeting a 2.0 release sometime in first quarter next year14:06
airship-irc-bot<sidney.shiba> @mattmceuen et al., I am creating a patch set (phases.yaml and executors.yaml) for the bootstrap container for Azure, GCP and Openstack. As you know, these manifests are simple to review and my question for you is do you prefer to have one patch set for each provider or can I have them grouped in a single one? Note that there are three phases per provider. Example of one phase and executor provided below: _Azure phase_: `# This15:53
airship-irc-botphase triggers the deployment of an ephemeral cluster` `# on Azure Cloud platform` `apiVersion: airshipit.org/v1alpha1` `kind: Phase` `metadata:`   `name: ephemeral-az-genesis` `config:`   `executorRef:`     `apiVersion: airshipit.org/v1alpha1`     `kind: BootConfiguration`     `name: ephemeral-az-genesis`  Executor: `# This executor launchs a bootstrap container, which creates` `# an Azure Kubernetes Service (AKS) cluster` `apiVersion:15:53
airship-irc-botairshipit.org/v1alpha1` `kind: BootConfiguration` `metadata:`   `name: ephemeral-az-genesis`   `labels:`     `airshipit.org/deploy-k8s: "false"` `ephemeralCluster:`   `bootstrapCommand: create`   `configFilename: azure-config.yaml` `bootstrapContainer:`   `containerRuntime: docker`   `image: quay.io/airshipit/capz-bootstrap:latest`   `volume: /home/esidshi/.airship:/kube`   `kubeconfig: capz.kubeconfig`15:53
*** muhaha has joined #airshipit16:14
airship-irc-bot<sb464f> Hi Team i am able to get the gates passing for this IPA changes can i get some eyes on this change please -> https://review.opendev.org/c/airship/airshipctl/+/76537616:56
airship-irc-bot<sirajudeen.yasin> Can i request some reviews on these PSs https://review.opendev.org/c/airship/airshipctl/+/762773 => Deploy Calico using Tigera Operator https://review.opendev.org/c/airship/airshipctl/+/766228 => Image override for cluster components https://review.opendev.org/c/airship/airshipctl/+/765165 => customize Log collection for other Providers https://review.opendev.org/c/airship/airshipctl/+/766427 => Revert "Use global17:04
airship-irc-botcertmanager for clusterctl" => To preserve upstream manifests as is17:04
*** sreejithp has joined #airshipit17:57
mattmceuen@sidney.shiba -- agree, since it's a small change per-provider, combining them together into one patchset will likely make it easier to review, rather than harder18:06
airship-irc-bot<sidney.shiba> Thanks Matt.18:08
*** sreejithp_ has joined #airshipit19:15
*** sreejithp has quit IRC19:17
airship-irc-bot<sb464f> looking for one more review on this -> https://review.opendev.org/c/airship/airshipctl/+/76537619:50
*** muhaha has quit IRC19:53
airship-irc-bot<mf4716> thank you @kk6740 for your +2 and WF+1 for @sb464f’s PS - thanks @dwalt for your +2/review too19:57
*** muhaha has joined #airshipit19:58
*** muhaha has quit IRC21:30
*** sreejithp has joined #airshipit22:37
*** sreejithp_ has quit IRC22:37
*** sreejithp has quit IRC22:38

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!