What needs to happen for official Fedora in GCE?

[Matthew Miller]

Hi everyone. As promised at the meeting two weeks ago, here is an email
about this. :) 

I think the goal here is (and correct me if I'm wrong):

 a) a "semi-official" F20 image in GCE as soon as possible
 b) actually-official F21 images (for all of our spins)

See https://fedorahosted.org/cloud/ticket/5 for the blockers. I think these
are both resolved in F21 but the GCE datasource isn't yet in cloud-init in
F20. So, there are really two parallel lines of work here:

 a) producing and uploading the ad-hoc F20 image (possily as a remix, if we
    don't get a cloud-init update
 b) figuring out what release engineering and quality assurance needs we
    have for F21, and... someone to do those things. (If we have an easy
    upload process which uses open-source tools included in Fedora, it'll be
    easy for Fedora Rel-Eng to add that to the current process. Better,
    we'll want it integrated into the planned _automatic_ process.)

Anything I'm missing here?
-- 
Matthew Miller    --   Fedora Project    --    <mattdm(a)fedoraproject.org&gt;
                                  "Tepid change for the somewhat better!"

[Eric Johnson]

Did you already take care of making sure the Google daemons get added to
the image and fire up on instance boot?  Sorry, if that already happened
before I started camping out here.

If not, then I'm not sure if/where that would fit in with the F20 image but
probably should make it into F21 (since you called it "actually-official").


On Thu, May 15, 2014 at 6:25 AM, Matthew Miller <mattdm(a)fedoraproject.org&gt;wrote:

>  Hi everyone. As promised at the meeting two weeks ago, here is an
> email
>  about this. :)
>
>  I think the goal here is (and correct me if I'm wrong):
>
>   a) a "semi-official" F20 image in GCE as soon as possible
>   b) actually-official F21 images (for all of our spins)
>
>  See https://fedorahosted.org/cloud/ticket/5 for the blockers. I think
>  these
>  are both resolved in F21 but the GCE datasource isn't yet in cloud-init in
>  F20. So, there are really two parallel lines of work here:
>
>   a) producing and uploading the ad-hoc F20 image (possily as a remix, if we
>      don't get a cloud-init update
>   b) figuring out what release engineering and quality assurance needs we
>      have for F21, and... someone to do those things. (If we have an easy
>      upload process which uses open-source tools included in Fedora, it'll
>  be
>      easy for Fedora Rel-Eng to add that to the current process. Better,
>      we'll want it integrated into the planned _automatic_ process.)
>
>  Anything I'm missing here?
>  --
>  Matthew Miller    --   Fedora Project    --    <mattdm(a)fedoraproject.org&gt;
>                                    "Tepid change for the somewhat better!"
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>

[Vaidas Jablonskis]

I wrote GCE datasource support for cloud-init and submitted upstream few
months ago which is now released -
https://launchpad.net/cloud-init/trunk/0.7.5 . Not sure if this helps in
any way. I have been running f20 in GCE in production for a long time now:
https://github.com/vaijab/fedora-gce-image

Let me know if I can be useful with anything.

Thanks,
Vaidas


On 15 May 2014 14:25, Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:

>  Hi everyone. As promised at the meeting two weeks ago, here is an
> email
>  about this. :)
>
>  I think the goal here is (and correct me if I'm wrong):
>
>   a) a "semi-official" F20 image in GCE as soon as possible
>   b) actually-official F21 images (for all of our spins)
>
>  See https://fedorahosted.org/cloud/ticket/5 for the blockers. I think
>  these
>  are both resolved in F21 but the GCE datasource isn't yet in cloud-init in
>  F20. So, there are really two parallel lines of work here:
>
>   a) producing and uploading the ad-hoc F20 image (possily as a remix, if we
>      don't get a cloud-init update
>   b) figuring out what release engineering and quality assurance needs we
>      have for F21, and... someone to do those things. (If we have an easy
>      upload process which uses open-source tools included in Fedora, it'll
>  be
>      easy for Fedora Rel-Eng to add that to the current process. Better,
>      we'll want it integrated into the planned _automatic_ process.)
>
>  Anything I'm missing here?
>  --
>  Matthew Miller    --   Fedora Project    --    <mattdm(a)fedoraproject.org&gt;
>                                    "Tepid change for the somewhat better!"
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  


-- 
Vaidas Jablonskis

[Sam Kottler]

On 5/15/14, 7:35 PM, Vaidas Jablonskis wrote:
>  I wrote GCE datasource support for cloud-init and submitted upstream
>  few months ago which is now released
>  - https://launchpad.net/cloud-init/trunk/0.7.5 . Not sure if this
>  helps in any way. I have been running f20 in GCE in production for a
>  long time now: https://github.com/vaijab/fedora-gce-image 
I recently updated rawhide to cloud-init 0.7.5 and there's no reason it
couldn't get merged back into f20.

>  Let me know if I can be useful with anything.
>
>  Thanks,
>  Vaidas
>
>
>  On 15 May 2014 14:25, Matthew Miller <mattdm(a)fedoraproject.org
>  <mailto:[e-mail]>> wrote:
>
>      Hi everyone. As promised at the meeting two weeks ago, here is an
>      email
>      about this. :)
>
>      I think the goal here is (and correct me if I'm wrong):
>
>       a) a "semi-official" F20 image in GCE as soon as possible
>       b) actually-official F21 images (for all of our spins)
>
>      See https://fedorahosted.org/cloud/ticket/5 for the blockers. I
>      think these
>      are both resolved in F21 but the GCE datasource isn't yet in
>      cloud-init in
>      F20. So, there are really two parallel lines of work here:
>
>       a) producing and uploading the ad-hoc F20 image (possily as a
>      remix, if we
>          don't get a cloud-init update
>       b) figuring out what release engineering and quality assurance
>      needs we
>          have for F21, and... someone to do those things. (If we have
>      an easy
>          upload process which uses open-source tools included in
>      Fedora, it'll be
>          easy for Fedora Rel-Eng to add that to the current process.
>      Better,
>          we'll want it integrated into the planned _automatic_ process.)
>
>      Anything I'm missing here?
>      --
>      Matthew Miller    --   Fedora Project    --  
>       <mattdm(a)fedoraproject.org <mailto:[e-mail]>>
>                                        "Tepid change for the somewhat
>      better!"
>      _______________________________________________
>      cloud mailing list
>      cloud(a)lists.fedoraproject.org <mailto:[e-mail]>
>      https://admin.fedoraproject.org/mailman/listinfo/cloud
>      Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
>
>
>
>  -- 
>  Vaidas Jablonskis
>
>
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 15 May 2014 09:25:25 -0400
Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:

>  Hi everyone. As promised at the meeting two weeks ago, here is an
>  email about this. :) 
>  
>  I think the goal here is (and correct me if I'm wrong):
>  
>   a) a "semi-official" F20 image in GCE as soon as possible
>   b) actually-official F21 images (for all of our spins)
>  
>  See https://fedorahosted.org/cloud/ticket/5 for the blockers. I think
>  these are both resolved in F21 but the GCE datasource isn't yet in
>  cloud-init in F20. So, there are really two parallel lines of work
>  here:
>  
>   a) producing and uploading the ad-hoc F20 image (possily as a remix,
>  if we don't get a cloud-init update
>   b) figuring out what release engineering and quality assurance needs
>  we have for F21, and... someone to do those things. (If we have an
>  easy upload process which uses open-source tools included in Fedora,
>  it'll be easy for Fedora Rel-Eng to add that to the current process.
>  Better, we'll want it integrated into the planned _automatic_
>  process.)
>  
if it doesnt have open source uploading tools and we have to use
proprietary tools to do it it will not be done. we have a requirement
that everything has to be open. 

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBAgAGBQJTdMkUAAoJEH7ltONmPFDRYQ8P/jh5HVSaposF/4SR0qOyNJKP
> ummqgk+wDMzxNz1ixRgsBDkSzJCoojQduGUea8nmXqO/+wbyU9N0lodC04kNftdq
> 9cBDrlNdI4+D0eSwQYEEPjt8EUk8+Wlo6qBiR/CaRgdTwheXoMND/aqAeWFwxPV2
> guQqXhAPyZkHW3wqzCTcIOhxlwHa/XZh5H4LWjpEsckMjsDNQZbe/rmsL2CQxDFN
> 1HVppwsfBGgJazjoZTeiavp3H/97JgydJVLJC55OmCWpbyJw4TG9NeIUj3w8OZOo
> bBrbzO878W11TUw0vQvWwatK8ELv2IKmNc+/f5g9mbFMJV2BsTUrN6FHE6ihSTEg
> uEVwQTkDr+sy0JR7Sw6HhvBCbUAsf7g7slydYxh8s8bOOrNvHmZS/RHpLFRmFCA6
> XlnHLr6Sg/tS7S+dV7MN+wEGou09weHnLdfplpzq/NgLgiix+4Ah2SIbZVlv+bI5
> JJRq+E9NoCIaoRLbwKl6n1j8PO8pBObirodDteKXLGCLXSMEmE2x8Uokf/+3Z2Bt
> qmtVoRVX62NG7wEhJfWGFXDXSdXE5PzcNVt1NE0X3WUhOflJaDZ//KtjKVd9fNX9
> 8uAV22xtsWI/sHjEnWOAFq28Bq7GmJW+DOZEHbLM7IYlkUnmAcPzmRJi1Vn/aPDX
> gbsnppUhrhVhcG/8LVkq
> =8t3R
> -----END PGP SIGNATURE-----
>

[Vaidas Jablonskis]

GCE provides very nice APIs, so basically to upload a new image all is
needed is a couple of curl requests.


On 15 May 2014 15:03, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:

>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  On Thu, 15 May 2014 09:25:25 -0400
>  Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>
>  > Hi everyone. As promised at the meeting two weeks ago, here is an
>  > email about this. :)
>  >
>  > I think the goal here is (and correct me if I'm wrong):
>  >
>  >  a) a "semi-official" F20 image in GCE as soon as possible
>  >  b) actually-official F21 images (for all of our spins)
>  >
>  > See https://fedorahosted.org/cloud/ticket/5 for the blockers. I think
>  > these are both resolved in F21 but the GCE datasource isn't yet in
>  > cloud-init in F20. So, there are really two parallel lines of work
>  > here:
>  >
>  >  a) producing and uploading the ad-hoc F20 image (possily as a remix,
>  > if we don't get a cloud-init update
>  >  b) figuring out what release engineering and quality assurance needs
>  > we have for F21, and... someone to do those things. (If we have an
>  > easy upload process which uses open-source tools included in Fedora,
>  > it'll be easy for Fedora Rel-Eng to add that to the current process.
>  > Better, we'll want it integrated into the planned _automatic_
>  > process.)
>
>  if it doesnt have open source uploading tools and we have to use
>  proprietary tools to do it it will not be done. we have a requirement
>  that everything has to be open.
>
>  Dennis
> >  -----BEGIN PGP SIGNATURE-----
> >  Version: GnuPG v2.0.22 (GNU/Linux)
> >
> >  iQIcBAEBAgAGBQJTdMkUAAoJEH7ltONmPFDRYQ8P/jh5HVSaposF/4SR0qOyNJKP
> >  ummqgk+wDMzxNz1ixRgsBDkSzJCoojQduGUea8nmXqO/+wbyU9N0lodC04kNftdq
> >  9cBDrlNdI4+D0eSwQYEEPjt8EUk8+Wlo6qBiR/CaRgdTwheXoMND/aqAeWFwxPV2
> >  guQqXhAPyZkHW3wqzCTcIOhxlwHa/XZh5H4LWjpEsckMjsDNQZbe/rmsL2CQxDFN
> >  1HVppwsfBGgJazjoZTeiavp3H/97JgydJVLJC55OmCWpbyJw4TG9NeIUj3w8OZOo
> >  bBrbzO878W11TUw0vQvWwatK8ELv2IKmNc+/f5g9mbFMJV2BsTUrN6FHE6ihSTEg
> >  uEVwQTkDr+sy0JR7Sw6HhvBCbUAsf7g7slydYxh8s8bOOrNvHmZS/RHpLFRmFCA6
> >  XlnHLr6Sg/tS7S+dV7MN+wEGou09weHnLdfplpzq/NgLgiix+4Ah2SIbZVlv+bI5
> >  JJRq+E9NoCIaoRLbwKl6n1j8PO8pBObirodDteKXLGCLXSMEmE2x8Uokf/+3Z2Bt
> >  qmtVoRVX62NG7wEhJfWGFXDXSdXE5PzcNVt1NE0X3WUhOflJaDZ//KtjKVd9fNX9
> >  8uAV22xtsWI/sHjEnWOAFq28Bq7GmJW+DOZEHbLM7IYlkUnmAcPzmRJi1Vn/aPDX
> >  gbsnppUhrhVhcG/8LVkq
> >  =8t3R
> >  -----END PGP SIGNATURE----- 
>  _______________________________________________
>  cloud mailing list
>  cloud(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/cloud
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  


-- 
Vaidas Jablonskis