Hi all,
On last year, we decided that our Cloud Orchestrator for ClearLinux would be CIAO<https://clearlinux.org/ciao> Project. At that moment, the only OpenStack pieces that we kept in ClearLinux were Keystone (identity service) and OpenStack clients.
On last weeks we have been experiencing so much trouble with Keystone and its dependencies. All of this is because the hard requirements that Keystone has with certain packages that cannot be upgraded.
We have decided to remove Keystone service support from ClearLinux.
Why?
· As Keystone’s python3 support is still in progress, it affects ClearLinux’s plans for machine learning software which is mostly python3 developed.
o We want to ship python3 versions of software that will be required for Machine Learning usages.
· Keystone is not fitting with the ClearLinux’s philosophy of rolling release and having latest software versions.
· Keystone’s dependencies are really sensitive and a single dependency upgrade could cause a major damage.
We’ll only keep the OpenStack clients which don’t have any trouble with being on latest release. They are also Python2/Python3 build-able.
We encourage you to take a look on Ciao Project<https://clearlinux.org/ciao>.
Regards,
--
Obed N Munoz
Cloud Engineer @ ClearLinux Project
Open Source Technology Center
Package krb5-dev: /usr/include/krb5/krb5.h, line 8320:
#include <et/com_err.h>
This file is part of e2fsprogs-dev. e2fsprogs-dev is not listed as a dependency of the krb5-dev RPM.
Note, I ran into this while building packages with autospec and thus using Yum and RPMs.
Ben
It appears all of the Makefiles in the clearlinux-pkgs repos have an include of ../common/Makefile.common. Is there a parent repository for these package repositories?
Thanks,
Ben
The current flake8 package needs mccabe<0.7.0,>=0.6.0. Currently mccabe 0.5.2 is available.
vagrant(a)clr-94ba9f0123c4422dade67c18df0c63ff ~ $ flake8
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 659, in _build_master
ws.require(__requires__)
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 967, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 858, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (mccabe 0.5.2 (/usr/lib/python3.6/site-packages), Requirement.parse('mccabe<0.7.0,>=0.6.0'), {'flake8'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/flake8", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3017, in <module>
@_call_aside
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3003, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3030, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 661, in _build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 674, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 853, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'mccabe<0.7.0,>=0.6.0' distribution was not found and is required by flake8
Ben
It looks like as of 13520, kernel-lts has moved to 4.9.10. This release is missing VirtualBox kernel modules and the handy install-vbox-lga script.
Also both the clearlinux-pkgs/linux-lts and clearlinux-pkgs/linux Github repos haven't been updated to reflect the current packages. Is this normal, i.e. pushing updated packages before updating the package repo?
Thanks,
Ben
Hi William,
Thanks for the tip. Also the instructions probably should be updated to specify CERT=<path>/Swupd_Root.pem in builder.conf, or add a step to copy ClearLinuxRoot.pem to Swupd_Root.pem.
Ben
> On Feb 22, 2017, at 11:20 AM, Douglas, William <william.douglas(a)intel.com> wrote:
>
> Hi Ben,
>
> On Wed, Feb 22, 2017 at 7:04 AM, Allen, Benjamin S.
> <bsallen(a)alcf.anl.gov> wrote:
>> Following https://clearlinux.org/documentation/mixer.html. At the step to run ister.py to generate an image, swupd verify fails on validating the Manifest.Mom:
>>
>> Cmd: ister.py -t release-image-config.json -V file:///media/mixer/update/www/ -C file:///media/mixer/update/www/ -f 1
>>
>
> Unfortunately you've been bit by out of date instructions. We'll try
> and get a fix to that soon.
>
> You can add a -s option to the ister command and give it the path to
> the Swupd_Root.pem file that mixer creates. For example if my current
> directory has the pem file in it, I'd do:
> # ister.py -t release-image-config.json -V
> file:///media/mixer/update/www/ -C file:///media/mixer/update/www/ -f
> 1 -s ./
>
> Hopefully that fixes your issue.
>
>
> Thanks,
> William
Good Morning,
We are a research and development company that is looking into the use of
containers in a highly secure manor. I was wondering if we could get some
information or get a demo that can get us more information about the Clear
Linux project. I specific focus would be how clear might allow for greater
MAC within a container
Regards,
Erik Carlson, MBA, CISSP
Direct (240)436-2299
