[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`

2017-03-01 Thread Christoph Görn 

goern added a new comment to an issue you are following:
``
> Does next Friday work for people?  Or is that too hard on the Europeans?

I will be in Westford, so next Fri I am not an European...
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/238
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

2017-03-01 Thread Dusty Mabe 


On 03/01/2017 09:25 AM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree commit:
> 
> Commit: ba95a4665776b58d342ad9cc36779f9b8fcf19c6606f8964a8ec1622cadc
> Version: 25.67
> 
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/cloud/download/atomic.html
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20170228.0/Atomic/x86_64/iso/Fedora-Atomic-25-20170228.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20170228.0/CloudImages/x86_64/images/Fedora-CloudImages-25-20170228.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Cloud Wiki space.
> 
> https://fedoraproject.org/wiki/Cloud#Quick_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering
> 

The Vagrant Atlas page with the new atomic host:

https://atlas.hashicorp.com/fedora/boxes/
https://atlas.hashicorp.com/fedora/boxes/25-atomic-host/versions/20170228

vagrant init fedora/25-atomic-host; vagrant up

or, if you already have the box, to get the new one:

vagrant box update --box fedora/25-atomic-host

- Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Cloud AMIs are not readable

2017-03-01 Thread Dusty Mabe 


On 03/01/2017 12:08 PM, Sayan Chowdhury wrote:
> On Tue, Feb 28, 2017 at 9:43 PM, Sayan Chowdhury
>  wrote:
>> On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen  
>> wrote:
>>> We are still working on this.
>>>
>>> On 27 February 2017 at 20:11, Matthew Miller  
>>> wrote:
 On Thu, Feb 23, 2017 at 09:40:53AM -0700, Kevin Fenzi wrote:
>> Neither me or Kushal has access to the account. So, somebody who has
>> access to the account can go to the snapshot page and make the
>> Snapshots public.
> Hum. Who would that be then? Just Dennis?

 Did we find the answer to this? I have the account information recorded
 in an encrypted file just in case.
>>
>> I have written a script just haven't tested it. The script makes all
>> the snapshots we have public. That should work for now.
>>
> 
> Here is the script[1] that should make all the AMIs ready to be copied
> [1] https://gist.github.com/sayanchowdhury/ffbc1f847ba84d47a454e4fd3cc603fd
> 

LGTM
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Cloud Meeting Minutes 2017-03-01

2017-03-01 Thread Dusty Mabe 

summary: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-01/atomic_wg.2017-03-01-17.02.html
full log: 
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-01/atomic_wg.2017-03-01-17.02.log.html


#fedora-meeting-1: atomic_wg



Meeting started by roshi at 17:02:11 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-03-01/atomic_wg.2017-03-01-17.02.log.html
.



Meeting summary
---
* Roll Call  (roshi, 17:02:20)

* Decide on version scheme for F26  (roshi, 17:04:16)
  * LINK: https://pagure.io/atomic-wg/issue/229   (roshi, 17:04:19)

* Previous Meeting Follow-Up  (roshi, 17:06:06)
  * ACTION: dusty to create atomic-wg page for future VFAD topics
(dustymabe, 17:08:01)
  * ACTION: sayan to create ticket on moving fedimg from libcloud to
boto  (dustymabe, 17:09:41)

* F26 naming scheme  (roshi, 17:10:23)
  * LINK: https://pagure.io/atomic-wg/issue/229   (roshi, 17:10:25)
  * LINK: https://fedoraproject.org/wiki/Cloud/VFAD_ideas   (jberkus,
17:15:27)
  * LINK: https://fedoraproject.org/wiki/Cloud/VFAD_ideas   (trishnag,
17:15:46)
  * AGREED: - use the $major.$datestamp.$serial for F26 and close the
ticket.  (roshi, 17:27:42)

* Planning first atomic VFAD  (roshi, 17:28:43)
  * LINK: https://pagure.io/atomic-wg/issue/201   (roshi, 17:28:45)

* Ship fedora-motd  (roshi, 17:30:06)
  * LINK: https://pagure.io/atomic-wg/issue/160   (roshi, 17:30:08)

* Fedora OpenShift Playground (FOSP)  (roshi, 17:36:49)
  * LINK: https://pagure.io/atomic-wg/issue/153   (roshi, 17:36:51)
  * Still waiting on hardware for the FOSP efforts  (roshi, 17:39:10)

* Open Floor  (roshi, 17:39:17)
  * LINK: https://pagure.io/atomic-wg/issues?status=Open&tags=containers
(dustymabe, 17:41:38)

Meeting ended at 17:54:27 UTC.




Action Items

* dusty to create atomic-wg page for future VFAD topics
* sayan to create ticket on moving fedimg from libcloud to boto




Action Items, by person
---
* sayan
  * sayan to create ticket on moving fedimg from libcloud to boto
* **UNASSIGNED**
  * dusty to create atomic-wg page for future VFAD topics




People Present (lines said)
---
* dustymabe (91)
* roshi (75)
* jberkus (54)
* zodbot (20)
* walters (17)
* kushal (8)
* jhogarth (8)
* jlebon (7)
* trishnag (6)
* gbraad (5)
* sayan (4)
* ksinny (4)
* jbrooks (4)
* miabbott (3)
* bowlofeggs (2)
* tflink (2)
* walters_ (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #233 `Container guidelines for systemd based containers`

2017-03-01 Thread Daniel J Walsh 

dwalsh added a new comment to an issue you are following:
``
BTW Even if we got oci-systemd-hook into debian, we would still need to get 
projectatomic/docker in since docker rejected the patch to run hooks directly.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/233
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`

2017-03-01 Thread Dusty Mabe 

The issue: `VFAD: Settle container policy open questions` of project: 
`atomic-wg` has been assigned to `jberkus` by dustymabe.

https://pagure.io/atomic-wg/issue/238
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #238 `VFAD: Settle container policy open questions`

2017-03-01 Thread Dusty Mabe 

dustymabe reported a new issue against the project: `atomic-wg` that you are 
following:
``
We have identified quite a few policy decisions that need to be made 
surrounding containers before we can start reviewing these things in bulk. Some 
of the issues are below:

- https://pagure.io/atomic-wg/issue/235
- https://pagure.io/atomic-wg/issue/234
- https://pagure.io/atomic-wg/issue/233


We need to have a group of people really get together and hash these issues out 
and publish the results so that we can start reviewing containers at a faster 
rate. I am giving the point on this to @jberkus as discussed in today's IRC 
meeting. A VFAD next week would probably be a great way to hash out some of 
this and get decisions back to users and reviewers fast.

other interested parties that want to take part in the discussion are @gbraad, 
@kushal, @jhogarth. It's also required that @maxamillion be there and would 
probably be good to have @jbrooks there. I'll add more names as I find people. 

 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/238
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #237 `Migrate fedimg EC2Service from libcloud to boto`

2017-03-01 Thread Dusty Mabe 

dustymabe added a new comment to an issue you are following:
``
I think we have periodically been bumping up against limitations of libcloud 
(from what I hear from sayan) and if that is the case then we should consider 
making this move. That is, unless libcloud upstream is active and working to 
close gaps. 

One thing to consider is that if we branch out to other clouds for uploading 
images would we use $CLOUD_API_SOFTWARE or would we try to use libcloud there? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/237
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #237 `Migrate fedimg EC2Service from libcloud to boto`

2017-03-01 Thread Sayan Chowdhury 

sayanchowdhury reported a new issue against the project: `atomic-wg` that you 
are following:
``
fedimg `EC2Service` right now uses libcloud to create the AMIs. Libcloud does 
not support a lot of features whereas boto has a better documentation and 
provides the missing bits. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/237
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #186 `switch to overlay2`

2017-03-01 Thread Dusty Mabe 

The issue: `switch to overlay2` of project: `atomic-wg` has been assigned to 
`dustymabe` by dustymabe.

https://pagure.io/atomic-wg/issue/186
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Cloud AMIs are not readable

2017-03-01 Thread Sayan Chowdhury 
On Tue, Feb 28, 2017 at 9:43 PM, Sayan Chowdhury
 wrote:
> On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen  
> wrote:
>> We are still working on this.
>>
>> On 27 February 2017 at 20:11, Matthew Miller  
>> wrote:
>>> On Thu, Feb 23, 2017 at 09:40:53AM -0700, Kevin Fenzi wrote:
 > Neither me or Kushal has access to the account. So, somebody who has
 > access to the account can go to the snapshot page and make the
 > Snapshots public.
 Hum. Who would that be then? Just Dennis?
>>>
>>> Did we find the answer to this? I have the account information recorded
>>> in an encrypted file just in case.
>
> I have written a script just haven't tested it. The script makes all
> the snapshots we have public. That should work for now.
>

Here is the script[1] that should make all the AMIs ready to be copied
[1] https://gist.github.com/sayanchowdhury/ffbc1f847ba84d47a454e4fd3cc603fd


-- 
Sayan Chowdhury 
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

2017-03-01 Thread Kushal Das 

kushal added a new comment to an issue you are following:
``
> I'd vote for images having a simple serial number - in the case where we have 
> to respin the cloud image because we changed the kickstart but not the tree, 
> we'd go from -1 to -2 or so.
> i.e.:
> Fedora-Atomic-25.20170130.0-1.x86_64.qcow2
> 
I like this one.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/229
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #236 `container scratch build without a dist-git`

2017-03-01 Thread Dusty Mabe 

dustymabe added a new comment to an issue you are following:
``
@maxamillion can you answer this? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/236
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #198 `move ostree ref to be "container-host"`

2017-03-01 Thread Dusty Mabe 

The issue: `move ostree ref to be "container-host"` of project: `atomic-wg` has 
been assigned to `dustymabe` by dustymabe.

https://pagure.io/atomic-wg/issue/198
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #121 `Migrate Dockerfiles to systemd, update for Fedora:latest, clean up READMEs`

2017-03-01 Thread Dusty Mabe 

The status of the issue: `Migrate Dockerfiles to systemd, update for 
Fedora:latest, clean up READMEs` of project: `atomic-wg` has been updated to: 
Closed by dustymabe.

https://pagure.io/atomic-wg/issue/121
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #121 `Migrate Dockerfiles to systemd, update for Fedora:latest, clean up READMEs`

2017-03-01 Thread Dusty Mabe 

dustymabe added a new comment to an issue you are following:
``
closing this Dockerfiles ticket as we are now using the Fedora build system to 
build containers and they are going through review. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/121
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #127 `Working with the Server WG`

2017-03-01 Thread Dusty Mabe 

The status of the issue: `Working with the Server WG` of project: `atomic-wg` 
has been updated to: Closed by dustymabe.

https://pagure.io/atomic-wg/issue/127
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #127 `Working with the Server WG`

2017-03-01 Thread Dusty Mabe 

dustymabe added a new comment to an issue you are following:
``
Leaving the cloud base image with the cloud sig for now:

https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/thread/ITOEHIH2LJGUB6ZIOUYGOEX4T66JJKSX/#PEEAQVTK5TNDKFHXBRVMW7ZA5NKKYKT6
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/127
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #162 `Milestones, components need updating`

2017-03-01 Thread Dusty Mabe 

The status of the issue: `Milestones, components need updating` of project: 
`atomic-wg` has been updated to: Closed by dustymabe.

https://pagure.io/atomic-wg/issue/162
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement

2017-03-01 Thread Dusty Mabe 


On 03/01/2017 09:25 AM, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree commit:
> 
> Commit: ba95a4665776b58d342ad9cc36779f9b8fcf19c6606f8964a8ec1622cadc
> Version: 25.67
> 
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
> `atomic host deploy`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/cloud/download/atomic.html
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20170228.0/Atomic/x86_64/iso/Fedora-Atomic-25-20170228.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20170228.0/CloudImages/x86_64/images/Fedora-CloudImages-25-20170228.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
> 
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
> 
> For more information about the latest targets, please reference the Fedora
> Cloud Wiki space.
> 
> https://fedoraproject.org/wiki/Cloud#Quick_Links
> 
> Do note that it can take some of the mirrors up to 12 hours to "check-in" at
> their own discretion.
> 
> Thank you,
> Fedora Release Engineering

This release contains the following changes since last release from
5a9de04163a60c5f2771b3d307601fa4e2234f12b662c97e28290b7bcbdb43f0 to
ba95a4665776b58d342ad9cc36779f9b8fcf19c6606f8964a8ec1622cadc

Changed:
  audit 2.7.2-2.fc25 -> 2.7.3-1.fc25
  audit-libs 2.7.2-2.fc25 -> 2.7.3-1.fc25
  audit-libs-python 2.7.2-2.fc25 -> 2.7.3-1.fc25
  audit-libs-python3 2.7.2-2.fc25 -> 2.7.3-1.fc25
  cockpit-bridge 130-1.fc25 -> 131-1.fc25
  cockpit-docker 130-1.fc25 -> 131-1.fc25
  cockpit-networkmanager 130-1.fc25 -> 131-1.fc25
  cockpit-ostree 130-1.fc25 -> 131-1.fc25
  cockpit-system 130-1.fc25 -> 131-1.fc25
  container-selinux 2:2.5-1.fc25 -> 2:2.6-1.fc25
  crypto-policies 20160921-2.git75b9b04.fc25 -> 20160921-4.gitf3018dd.fc25
  dbus 1:1.11.8-1.fc25 -> 1:1.11.10-1.fc25
  dbus-libs 1:1.11.8-1.fc25 -> 1:1.11.10-1.fc25
  fedora-repos 25-1 -> 25-2
  glib2 2.50.2-1.fc25 -> 2.50.3-1.fc25
  gnutls 3.5.8-2.fc25 -> 3.5.9-2.fc25
  gomtree 0.3.0-1.fc25 -> 0.3.1-1.fc25
  grep 2.27-1.fc25 -> 2.27-2.fc25
  iptables 1.6.0-2.fc25 -> 1.6.0-3.fc25
  iptables-libs 1.6.0-2.fc25 -> 1.6.0-3.fc25
  iptables-services 1.6.0-2.fc25 -> 1.6.0-3.fc25
  kernel 4.9.9-200.fc25 -> 4.9.12-200.fc25
  kernel-core 4.9.9-200.fc25 -> 4.9.12-200.fc25
  kernel-modules 4.9.9-200.fc25 -> 4.9.12-200.fc25
  libblkid 2.28.2-1.fc25 -> 2.28.2-2.fc25
  libfdisk 2.28.2-1.fc25 -> 2.28.2-2.fc25
  libmount 2.28.2-1.fc25 -> 2.28.2-2.fc25
  libnetfilter_conntrack 1.0.4-6.fc24 -> 1.0.6-2.fc25
  libsmartcols 2.28.2-1.fc25 -> 2.28.2-2.fc25
  libsolv 0.6.25-1.fc25 -> 0.6.26-1.fc25
  libuuid 2.28.2-1.fc25 -> 2.28.2-2.fc25
  nfs-utils 1:2.1.1-1.fc25 -> 1:2.1.1-2.rc1.fc25
  openssh 7.4p1-2.fc25 -> 7.4p1-3.fc25
  openssh-clients 7.4p1-2.fc25 -> 7.4p1-3.fc25
  openssh-server 7.4p1-2.fc25 -> 7.4p1-3.fc25
  ostree 2017.1-2.fc25 -> 2017.2-3.fc25
  ostree-grub2 2017.1-2.fc25 -> 2017.2-3.fc25
  pcre 8.40-1.fc25 -> 8.40-4.fc25
  publicsuffix-list-dafsa 20170116-1.fc25 -> 20170206-1.fc25
  rpm-ostree 2016.13-1.fc25 -> 2017.2-2.fc25
  selinux-policy 3.13.1-225.6.fc25 -> 3.13.1-225.10.fc25
  selinux-policy-targeted 3.13.1-225.6.fc25 -> 3.13.1-225.10.fc25
  sos 3.2-4.fc25 -> 3.3-1.fc25
  strace 4.15-1.fc25 -> 4.16-1.fc25
  systemd 231-12.fc25 -> 231-14.fc25
  systemd-container 231-12.fc25 -> 231-14.fc25
  systemd-libs 231-12.fc25 -> 231-14.fc25
  systemd-pam 231-12.fc25 -> 231-14.fc25
  systemd-udev 231-12.fc25 -> 231-14.fc25
  util-linux 2.28.2-1.fc25 -> 2.28.2-2.fc25
  vim-minimal 2:8.0.324-1.fc25 -> 2:8.0.347-2.fc25
Added:
  ostree-libs-2017.2-3.fc25.x86_64

Note that this release contains kernel-4.9.12-200.fc25 which contains
the fix for CVE-2017-6074: DCCP double-free vulnerability.

Dusty

___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Ansible woes for FAO

2017-03-01 Thread Jason DeTiberus 
On Wed, Mar 1, 2017 at 10:25 AM, Michael Scherer 
wrote:

> Le mardi 28 février 2017 à 16:33 -0800, Josh Berkus a écrit :
> > Folks,
> >
> > Apparently Ansible-2.2.1 breaks OpenShift-Ansible.  The only other
> > version available, 2.1.2 is too old for Openshift-Ansible.  And attempts
> > to downgrade via pip result in dependency hell and fails.
> >
> > So, as of now, there is no way to install OpenShift using Fedora as the
> > Ansible node.  I had to use a CentOS container.
>
> So, to prevent that in the future, what about adding a ansible devel
> checkout as a test for openshift ansible ?
>
> This would help Ansible (since it would be tested on a huge workload),
> and Openshift ansible, by making sure nothing is broken forward ?
>

We are working towards that, but just haven't gotten there yet.

-- 
Jason DeTiberus


>
> --
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS
>
>
>
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
>
>
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Ansible woes for FAO

2017-03-01 Thread Michael Scherer 
Le mardi 28 février 2017 à 16:33 -0800, Josh Berkus a écrit :
> Folks,
> 
> Apparently Ansible-2.2.1 breaks OpenShift-Ansible.  The only other
> version available, 2.1.2 is too old for Openshift-Ansible.  And attempts
> to downgrade via pip result in dependency hell and fails.
> 
> So, as of now, there is no way to install OpenShift using Fedora as the
> Ansible node.  I had to use a CentOS container.

So, to prevent that in the future, what about adding a ansible devel
checkout as a test for openshift ansible ?

This would help Ansible (since it would be tested on a huge workload),
and Openshift ansible, by making sure nothing is broken forward ?

-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #225 `Review Container Request for owncload (replacement of Fedora-Dockerfiles GitHub)`

2017-03-01 Thread James Hogarth 

jhogarth added a new comment to an issue you are following:
``
Carrying out the review I believe will need these questions being answered:


https://pagure.io/atomic-wg/issue/233
https://pagure.io/atomic-wg/issue/234
https://pagure.io/atomic-wg/issue/235

``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/225
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Fedora Atomic Host Two Week Release Announcement

2017-03-01 Thread noreply 

A new Fedora Atomic Host update is available via an OSTree commit:

Commit: ba95a4665776b58d342ad9cc36779f9b8fcf19c6606f8964a8ec1622cadc
Version: 25.67


Existing systems can be upgraded in place via e.g. `atomic host upgrade` or
`atomic host deploy`.

Corresponding image media for new installations can be downloaded from:

https://getfedora.org/en/cloud/download/atomic.html

Respective signed CHECKSUM files can be found here:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20170228.0/Atomic/x86_64/iso/Fedora-Atomic-25-20170228.0-x86_64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20170228.0/CloudImages/x86_64/images/Fedora-CloudImages-25-20170228.0-x86_64-CHECKSUM

For direct download, the "latest" targets are always available here:
https://getfedora.org/atomic_iso_latest
https://getfedora.org/atomic_qcow2_latest
https://getfedora.org/atomic_raw_latest
https://getfedora.org/atomic_vagrant_libvirt_latest
https://getfedora.org/atomic_vagrant_virtualbox_latest

Filename fetching URLs are available here:
https://getfedora.org/atomic_iso_latest_filename
https://getfedora.org/atomic_qcow2_latest_filename
https://getfedora.org/atomic_raw_latest_filename
https://getfedora.org/atomic_vagrant_libvirt_latest_filename
https://getfedora.org/atomic_vagrant_virtualbox_latest_filename

For more information about the latest targets, please reference the Fedora
Cloud Wiki space.

https://fedoraproject.org/wiki/Cloud#Quick_Links

Do note that it can take some of the mirrors up to 12 hours to "check-in" at
their own discretion.

Thank you,
Fedora Release Engineering
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #235 `Container guidelines for versioning of packages in the container`

2017-03-01 Thread James Hogarth 

jhogarth reported a new issue against the project: `atomic-wg` that you are 
following:
``
Since the container build process uses stable repos it's tricky to time a 
container update alongside an update of key components.

It also leads to the question to the guidelines of "what does 'ENV 
NAME=myawesomecontainer VERSION=0.1 RELEASE=1 ARCH=x86_64' actually mean?"

In the case of the owncloud container review one would think it refers to 
owncloud itself (presently at 9.1.4) but the container also has httpd and php 
which may be susceptible to security issues and knowing the version within may 
be important.

There's also an issue of tying the version in the ENV to the actual package in 
place.

We should have something in the guidelines to ensure this. The RUN dnf -y 
install owncloud (in this instance) should probably have dnf -y install 
owncloud-${VERSION}-${RELEASE} in order to prevent race conditions, although 
this would have an effect on the proposed fortnightly build process with the 
timing between an RPM maintainer updating the package and the container 
maintainer presenting a container update.

We either need a way to attempt to automate this, accept failures and rebuilds 
or some other thing I haven't thought of.

In addition we should allow building the container from at least the testing 
repos, if not the koji buildroot or similar setup, to prevent a significant lag 
between an update in fedora and being able to provide that update in a 
container based service.

The worst case would be a package in updates-testing for a full week and a 
poorly timed move to stable with the next container build, as proposed 
elsewhere, two weeks away for a full three weeks for a potential vulnerability 
or major bug.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/235
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #234 `Container guidelines for containers with volumes`

2017-03-01 Thread James Hogarth 

jhogarth reported a new issue against the project: `atomic-wg` that you are 
following:
``
To protect persistent data it's common to use a VOLUME in the Dockerfile to 
automatically generate and mount a volume for the container on the host.

Best practice when running these containers should be to used a named volume at 
that point to ensure persistent when the container is updated.

If VOLUME is not in the Dockerfile then there is a risk of data loss on 
container updates with an admin not paying attention to which data should be 
persistent.

I'd suggest we should allow VOLUME in the guidelines for the container 
maintainer to be clear what is considered important data that must be persisted 
but we should have a way of making it clear what should be declared at runtime.

An example would be the owncloud container review request which makes the httpd 
and owncloud configuration directories volumes for persistence and allow 
customisation, and makes the owncloud data directory a volume to prevent data 
loss.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/234
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org