ce o/
>
> --
> You received this message because you are subscribed to the Google Groups
> "okd-wg" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to okd-wg+unsubscr...@googlegroups.com.
> To view this discussion on the web v
hat we want
is 'just give me a working API so I can run containers' and not 'all of
openshift stuffed into a single host'.
On Fri, Aug 16, 2019 at 11:36 AM Clayton Coleman
wrote:
>
>
> On Aug 16, 2019, at 11:29 AM, Michael Gugino wrote:
>
> Pretty much alr
w%40mail.gmail.com
> <https://groups.google.com/d/msgid/okd-wg/CADE%2BktTuSSUaZZ-vPYkOLHKiojM9%2B5qgQVtV1pS7z7eTcu7jdw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "
hift/machine-config-operator/pull/889
> (As well as generic kernel arguments)
I still see the distro as an implementation detail. The only thing I
can see different from atomic vs coreos is (first) boot-time
configuration. Just look at openshift-ansible today for an example of
how you can integrate
ooling.
On Thu, Jul 25, 2019 at 9:51 AM Clayton Coleman wrote:
>
> > On Jul 25, 2019, at 4:19 AM, Aleksandar Lazic
> > wrote:
> >
> > HI.
> >
> >> Am 25.07.2019 um 06:52 schrieb Michael Gugino:
> >> I think FCoS could be a mutable detail. To
ere, I wouldn't consider my
statements as advocating strongly in any direction. Surely FCoS is
the natural fit, but I think considering other distros merits
discussion.
On Wed, Jul 24, 2019 at 9:23 PM Clayton Coleman wrote:
>
> > On Jul 24, 2019, at 9:14 PM, Michael Gugino wrote:
>
he same.
On Wed, Jul 24, 2019 at 12:05 PM Clayton Coleman wrote:
>
>
>
>
> On Wed, Jul 24, 2019 at 10:40 AM Michael Gugino wrote:
>>
>> I tried FCoS prior to the release by using the assembler on github.
>> Too much secret sauce in how to actually construct an
(which might take just as
> long to get and not really be a step forward for folks vs 3), or other, more
> dramatic options. Have folks given FCoS a try this week?
> https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started/. That's
> a great place to get started
>
> As always PRs and fixes to 3.x will continue to be welcomed and that effort
> continues unabated.
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
--
Michael Gugino
Senior Software Engineer - OpenShift
mgug...@redhat.com
540-846-0304
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
m
> discourse. If we get a lot of momentum in our Discourse though over Slack we
> can consider what to do later.
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
--
Michael Gugino
Senior Software Engineer - Op
gt; dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
--
Michael Gugino
Senior Software Engineer - OpenShift
mgug...@redhat.com
540-846-0304
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
se_packages.yml specifies python-docker: this
> used to be in python-docker-py but modern versions of that package now
> provide docker-python. python-docker does exist in python-docker-3.x but
> this is incompatible with atomic-1.22 in the extras repo.
>
>
>
> If these items should
nent} is supposed to be substituted by something during the
> playbook processing.
>
>
>
> Neale
>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Michael Gugi
then i'd expect same TLS errors as for when the namedCertificates
> section is present.
>
>
> Dani
>
> [1]
> https://docs.openshift.com/container-platform/3.10/install_config/certificate_customization.html#configuring-custom-certificates
>
>
> ________
chitectures/2018/html/deploying_and_managing_openshift_3.9_on_amazon_web_services/red_hat_openshift_container_platform_prerequisites
>>
>> [3]
>> https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/aws-ansible
>
>
--
Michael Gugino
Senior Software Engineer - OpenShift
mgug...@redhat.com
540-846-0304
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
o define it for 3.9 ?
>
> openshift_hosted_infra_selector="node-role.kubernetes.io/infra=true"
>
> Regards,
>
> Charles
>
> On Thu, Apr 12, 2018 at 2:56 PM, Michael Gugino wrote:
>>
>> If you're installing an all-in-one, you need to set the la
annotation for every project
> created ?
> Do I have to report a bug to origin or openshif-ansible project ?
>
> Regards,
>
> Charles
>
> _______
> dev mailing list
> dev@lists.openshift.
rther?
>
> Thanks,
>
> Jared, (韦煜)
> Software developer
> Interested in open source software, big data, Linux
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshi
/rzE5UV
>
> Regards
>
> Charles
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Michael Gugino
Senior Software Engineer - OpenShift
mgug...@redhat.com
540-
-origin39/
>>
>> I think it's
>> ansible-playbook -e openshift_repos_enable_testing=true
>
>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Michael Gugino
Senior Software Engineer - OpenShift
mgug...@redhat.com
540-846-0304
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
dations for deploying any other than
>> released openshift code. If you're trying to deploy testing images /
>> rpms,
>> your setup is going to depend on what you're trying to accomplish. I
>> highly recommend deploying released code. That is the only way it's
&g
n what you're trying to accomplish. I
highly recommend deploying released code. That is the only way it's
going to
'just work.'
On Fri, Mar 16, 2018 at 4:41 PM, Charles Moulliard wrote:
>
>
> On Fri, Mar 16, 2018 at 8:57 PM, Michael Gugino wrote:
>>
>>
> openshift_deployment_type = origin
> ...
>
> ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml
>
> On Fri, Mar 16, 2018 at 8:44 PM, Michael Gugino wrote:
>>
>> I would start again with new hosts, probably the easiest way forward.
>> I recomm
gin37/ is not
> consistent
>
> Is there a way to download / install properly all the required origin rmps
> as ansible playbook fails ?
>
>
> On Fri, Mar 16, 2018 at 8:24 PM, Michael Gugino wrote:
>>
>> Charles,
>>
>> You cannot install 3.9 from the o
tall openshift cluster using ansible
> playbook ?
>
> Regards
>
> Charles
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Michael Gugino
Senior S
24 matches
Mail list logo