On Wed, Apr 24, 2019 at 12:19 AM Kevin Fenzi <kevin@scrye.com> wrote:
On 4/23/19 8:31 AM, Sinny Kumari wrote:
> On Tue, Apr 23, 2019 at 4:55 PM Stephen John Smoogen <smooge@gmail.com>
> wrote:
>
>>
>>
>> On Tue, 23 Apr 2019 at 06:09, Sayan Chowdhury <gmail@yudocaa.in> wrote:
>>
>>> Hi all,
>>>
>>> Autocloud[1] has been part of the early stages of the 2-week Atomic
>>> release process. AFAIK, it was built as a quick solution until
>>> taskotron was not ready. Autocloud has served us well but over the
>>> last year, we haven't pushed much to Autocloud and it's also mostly in
>>> maintenance mode. Another big reason now for deprecating Autocloud is
>>> that it's still in Python2.
>>>
>>> Are there any concerns if we go ahead deprecate Autocloud in Fedora 31?
>>>
>>>
>>
>> Deprecating it in Fedora 31 means that it goes away when Fedora 31 end of
>> lifes (which would be late 2021? or early 2022). Do you mean to stop it
>> sooner than that?
>>
>
> If we are using autocloud only for Fedora Atomic Host Two Week release, we
> should be able to deprecate it with F29 EOL [1]

Or could we move f29+ all to whatever is replacing it? (taskotron?)

It will be nice but I am not aware of any other system in place which would
replace checks performed by autocloud.

(CC'ed tflink and kparal)
Does taskotron provides capability to perform tests on Fedora cloud Images like booting images and other basic checks?
 
if we can do that we can just retire it as soon as that move is done and
we are happy with the new process.

kevin


_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org


--
http://sinny.io/