Fedora AWS Resource IDs migrates to longer format
by Sayan Chowdhury
In February 2018, AWS announced the migration of Resource IDs to
longer format. Post June 2018, all the new resources will be created
with longer IDs by default.[1]
This email is to announce that the Fedora AMIs has been migrated to
the longer resource IDs format. The new format will migrate from the
current 8-character string to a 17-character string. For example, if
the AMI IDs are like "ami-1234abc0", post the migration the AMI IDs
would be like "ami-1234567890abcdef0".
If you have any questions, drop an email to the list or drop in
#fedora-atomic or #fedora-cloud on Freenode IRC.
[1] https://aws.amazon.com/about-aws/whats-new/2018/02/longer-fo
rmat-resource-ids-are-now-available-in-amazon-ec2/
--
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
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!
5 years, 10 months
[atomic-wg] Issue #354: help.md file for each container
by Petr Hracek
phracek reported a new issue against the project: `atomic-wg` that you are following:
``
I thinks each container should provide to user some help page.
Fedora has requirement for providing such file https://fedoraproject.org/wiki/Container:Guidelines#Help_File
The help.md file should contain some required fields like:
- image name
- maintainer
- name
- description
- usage
- if container uses environment variables then section ENVIRONMENT VARIABLES
- if container exposes ports then also section SECURITY IMPLICATION
e.g. memcached help.md
~~~
% MEMCACHED(1) Container Image Pages
% Petr Hracek
% February 6, 2017
# NAME
memcached - Memcached is a high-performance, distributed memory object caching system
# DESCRIPTION
Memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.
The container itself consists of:
- fedora/f26 base image
- memcached RPM package
Files added to the container during docker build include: /files/memcached.sh
# USAGE
To get the memcached container image on your local system, run the following:
docker pull docker.io/modularitycontainers/memcached
# ENVIRONMENT VARIABLES
The image recognizes the following environment variables that you can set
during initialization be passing `-e VAR=VALUE` to the Docker run command.
| Variable name | Description |
| :----------------------- | ----------------------------------------------------------- |
| `MEMCACHED_DEBUG_MODE` | Increases verbosity for server and client. Parameter is -vv |
| `MEMCACHED_CACHE_SIZE` | Sets the size of RAM to use for item storage (in megabytes) |
| `MEMCACHED_CONNECTIONS` | The max simultaneous connections; default is 1024 |
| `MEMCACHED_THREADS` | Sets number of threads to use to process incoming requests |
# SECURITY IMPLICATIONS
Lists of security-related attributes that are opened to the host.
-p 11211:11211
Opens container port 11211 and maps it to the same port on the host.
# SEE ALSO
Memcached page
<https://memcached.org/>
~~~
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/354
5 years, 10 months
[atomic-wg] Issue #432: AH with Podman for CI tests only
by Brent Baude
baude reported a new issue against the project: `atomic-wg` that you are following:
``
The upstream libpod project (https://github.com/projectatomic/libpod/) would love to have an AH F27 variant without docker and with podman and its friends. This would be only used in our PAPR CI tests and perhaps for debug. We understand a more official project is in the works for this and is being tracked by issue #422.
Today we currently use an F27 cloud image and install the packages we need. We would prefer that this be done predeployment and use AH instead of cloud.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/432
5 years, 10 months
