I created new task for creating swap file and mount it.
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/tasks/swap.yml
It is handy in AWS where flavors does not have swap disk.
You can use it like:
tasks:
- import_tasks: "{{ tasks_path }}/swap.yml"
when:
-
Dne 17. 02. 20 v 21:50 Stephen John Smoogen napsal(a):
> Because ip addresses can change, and we do not have time to fix it in
> multiple places,
That was me.
We will be adding 9 machines. One by one. So my intention was to go with IP and
then after we are done (one week) flip
it to dns.
But
not modify fedora*.repo
It is probably needed for centos and other, but I needed just this.
Miroslav
Přeposlaná zpráva
Předmět: [ansible] do not modify fedora*.repo when deploying in AWS
Datum: Fri, 14 Feb 2020 13:27:04 + (UTC)
Od: Miroslav Suchý
Komu: sysadmin-memb
Dne 03. 12. 19 v 11:34 Miroslav Suchý napsal(a):
>> can't we just point them to the nagios
>> page?
> That is great idea. And to have there link to outage calendar as well.
I sent a PR and you can see it live now at:
https://status.fedoraproject.org/
Thanks Mikolai for quick re
Dne 30. 11. 19 v 21:31 Kevin Fenzi napsal(a):
> can't we just point them to the nagios
> page?
That is great idea. And to have there link to outage calendar as well.
> But how do you map those?
> Some examples:
>
> * If a mirrorlist alerts as down that does not mean the service is down
> to
Dne 28. 11. 19 v 1:29 Kevin Fenzi napsal(a):
> I am missing what capabilities you are wanting it to
> have?
* current page shows "Everything is OK" even when some service does not work. I
would at least expect some orange text
"There seems to be some problems, not acknowledged by admins yet".
*
Hi.
For long time, I plan to do something about
https://status.fedoraproject.org/
I think that manual updates of this page does not reflect the capabilities of
these century.
My question is: do we want to go SasS way? I found
https://www.statusdashboard.com/pricing
which would cost us $99
-swift_store 138G 107G 25G 82% /srv/node/device1
Miroslav
Dne 20. 11. 19 v 9:20 Miroslav Suchý napsal(a):
> In Openstack we have long list of images, which can be deleted. Or likely
> deleted.
>
> These are clearly old, and I will wipe it away on Monday unless somebody say
> otherwi
Dne 21. 11. 19 v 23:54 Kevin Fenzi napsal(a):
> I hope we can run it in openshift?
Yes. No problem with that.
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
signature.asc
Description: OpenPGP digital signature
In Openstack we have long list of images, which can be deleted. Or likely
deleted.
These are clearly old, and I will wipe it away on Monday unless somebody say
otherwise:
Fedora-Cloud-Base-28-1.1.ppc64
Fedora-Cloud-Base-28-1.1.ppc64le
Fedora-Cloud-Base-28-1.1.x86_64
Dne 25. 10. 19 v 20:44 Randy Barlow napsal(a):
There appears to be work starting on a brand new implementation:
https://github.com/xsuchy/fedora-packages-ng
This version looks like it'll be Python 3 compatible, though it is
quite new.
We can keep it in mind, thanks for sharing!
Yes. Give me
Dne 11. 10. 19 v 17:28 Kevin Fenzi napsal(a):
config and drop the vm back to 32gb memory, but it seems kind of crazy
that more memory would cause more slowness. ;(
Can this be caused by swappiness? More memory, the same swappiness ratio, it can cause more IO. I would try to lower
swappiness.
Dne 01. 10. 19 v 9:53 Peter Robinson napsal(a):
Warrantee generally doesn't cover moves but the DC shipping company
should have insurance to cover breakages they cause as mistakes
happen.
It is hard to claim something if the package does not have any visible damage. And I guess you will not
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
> - make fpaste work with paste.centos.org
+1
I use fpaste a lot. So please keep the functionality of fpaste. But I do not
care to which service it will communicate.
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
Hi,
it is my pleasure to announce that Pavel Raiskup (praiskup) joined the Copr
team. Pavel has been contributing to Copr
for long time in his free time. He has been maintaining Red Hat internal Copr
instance for long time. Now, he is joining
Copr team as his full time job. Pavel replaced Michal
Dne 25. 03. 19 v 14:49 Patrick Uiterwijk napsal(a):
> Additionally, I would not call it dead since I took it over, given
> that I've been adding new features to it over time.
> There's not a huge set of new features people have been asking for, so
> I've only been adding what I do hear about or
Dne 21. 03. 19 v 13:57 Neal Gompa napsal(a):
> Forgive me, but what does sigul do that signd cannot? I'm unaware of
> any material differences between the two.
When I started Copr I considered both Sigul and OBS signd. I spent several
hours with Mirek Trmač - original author of
Sigul and we
Dne 27. 02. 19 v 23:00 Peter Robinson napsal(a):
>> Hey everyone.
>>
>> As you know, we currently have a RHOSP5 ancient cloud. After a bunch of
>> work last year, we got a RHOSP13 cloud up and mostly working, but it was
>> a ton of work. After hearing from the Fedora Council and our various
>>
Dne 14. 11. 18 v 2:20 Kevin Fenzi napsal(a):
> So, if you had slow pagure connections in the past, can you:
>
> * do some initial tests:
>
> time git clone https://pagure.io/pagure.git
Tested from Brno RH office.
real0m10,942s
user0m7,328s
sys 0m1,965s
> time curl
Dne 12. 11. 18 v 15:41 Miroslav Suchý napsal(a):
> Some times ago, I led student bachelor thesis and he added rpm support for
> Debian's PopCon [1], which is opt-in system
> to report package usage.
Ahh, forgot to add link to the port:
https://github.com/xsuchy/popcon-for-fedora-old
Dne 05. 11. 18 v 16:21 Stephen John Smoogen napsal(a):
> Currently there is no way to know what
> packages are being installed/downloaded the most.
Some times ago, I led student bachelor thesis and he added rpm support for
Debian's PopCon [1], which is opt-in system
to report package usage.
Dne 22.10.2018 v 18:18 Miroslav Suchý napsal(a):
> Dne 18.10.2018 v 21:08 Kevin Fenzi napsal(a):
>> Purging old eol data should slow that? Any idea how much?
>
> du tells me that:
>
> fedora-21-* 82 GB
> fedora-22-* 132 GB
> fedora-23-* 241 GB
> fedora-24-* 343 GB
Dne 18.10.2018 v 21:08 Kevin Fenzi napsal(a):
> Purging old eol data should slow that? Any idea how much?
du tells me that:
fedora-21-* 82 GB
fedora-22-* 132 GB
fedora-23-* 241 GB
fedora-24-* 343 GB
fedora-25-* 438 GB
fedora-26-* 775 GB
epel-5-* 9.7 GB
and I have some more time to check:
. Name service error
for name=petetravis.com type=A: Host not found
--- Begin Message ---
commit 4d57437c163d156b79dd212c6587ca03a78c077a
Author: Miroslav Suchý
Date: Wed Oct 17 11:04:08 2018 +0200
copr: generate index for subdirs of /archive/spacewalk/
roles/copr/backend/files
Dne 12.10.2018 v 22:11 Kevin Fenzi napsal(a):
> How much do we have left on that device?
At the end I added 1TB. Now we have:
/dev/vdc1 7.5T 6.2T 1.3T 83% /var/lib/copr/public_html
I attached the graph showing the history (sorry for the gap in 2015,2016).
But the end of the story is
FYI - We are running out of space on copr-be.cloud.fedoraproject.org:
/dev/vdc1 6.4T 6.4T 75G 99% /var/lib/copr/public_html
This is where repositories are stored. We likely run out of space till Monday.
Therefore I will add some space to this
volume from openstack - I plan to add 500
I want to set up monitoring of free space on /srv of retrace.fedoraproject.org.
It is huge volume therefore normal
check_disk_/srv does not have sense. I created new check, but it is my first
time working with nrpe. I would welcome if
someone can review it, before I push it.
Patch is in the
Dne 18.4.2018 v 23:31 Kevin Fenzi napsal(a):
> What would everyone think of moving the meeting to 16UTC?
> Or is there a better time for anyone?
+1
I cannot attend at 18UTC, but 16UTC is much better for me.
Miroslav
signature.asc
Description: OpenPGP digital signature
Can someone comment on this?
I am not really sure if there are some issues on mirrors (not likely) or if
this is some issue with Fedora Cloud when
network is overloaded (more likely).
Miroslav
Přeposlaná zpráva
Předmět: mirror failures
Datum: Mon, 9 Apr 2018 09:38:04 +0200
Hi,
what is the status of the new openstack instance? The old one is becoming pain
with every new day.
Miroslav
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to
Dne 5.4.2018 v 04:16 Neal Gompa napsal(a):
> The main problem, of course, is finding someone who wants to run it...
Even if you find someone (not as big problem), that guy basically cannot do
anything else. So basically strike out
something from our TODO list as CANNOT FIX.
@Justin thank you
channels.
:((
My username is: msuchy
Miroslav
> On 23 February 2018 at 11:17, Miroslav Suchý <msu...@redhat.com> wrote:
>> Dne 23.2.2018 v 10:57 Clement Verna napsal(a):
>>> Miroslav,
>>>
>>> Can you access https://fedoramagazine.org/wp-admin/edit.php ?
Dne 16.2.2018 v 14:56 Dusty Mabe napsal(a):
> Once we get it into Fedora this would be a great blog post for the magazine.
> What do you think?
Yes. Sure.
Miroslav
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To
After I seen the talk about VDO:
https://www.youtube.com/watch?v=7CGr5LEAfRY
I went ahead and tried it.
I tried it on small (12GB) sample of Copr data and I saved 20-30% data.
I then deployed it on production server retrace.fedoraproject.org and saved
there 15% out of 2TB.
Several notes: The
Dne 19.12.2017 v 16:41 Miroslav Suchý napsal(a):
> I plan to do that tomorrow.
Done.
However after the testing I end up with copr-be-dev-data volume in Detaching
state (it is in this state for more than 20
hours). I hope that it will eventually time-out during Christmass. But if
anyone kn
We are running out of disk space in Copr. It will probably run out during
Christmas so I am going to act before the weekend.
Right now we have 4GB volume for production and 4GB for dev machine (just
because we can, but we never used that). My
plan is to shrink dev volume to 150 GB. And allocate
Dne 11.12.2017 v 11:46 Patrick Uiterwijk napsal(a):
> Due to known security issues, the current Fedora Cloud's API is not
> available from the public internet.
1) then it should be changed in the playbook.
2) so how can I communicate with API from the fedora cloud itself? I am focused
on
Dne 21.11.2017 v 06:43 Marut Pandya napsal(a):
> How do i join fi-apprentice group?
> My login name is- pandyamarut
> please send me invite.
You should attend Fedora Infra meeting:
https://fedoraproject.org/wiki/Infrastructure/Meetings
introduce yourself, tell everyone what you would like to
) but it should be
done for common images (i.e.,
Fedora-Cloud-Base-27-1.6.x86_64.qcow2)
Miroslav Suchý
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Dne 1.11.2017 v 16:37 Kevin Fenzi napsal(a):
> On 11/01/2017 05:32 AM, Miroslav Suchý wrote:
>> Hi,
>> Copr is using up to 29 x86 VMs and 10 ppc VMs from Fedora Cloud for builders.
>> We are hitting the limits quite often. So I would like to ask if I can
>> assign anoth
Hi,
Copr is using up to 29 x86 VMs and 10 ppc VMs from Fedora Cloud for builders.
We are hitting the limits quite often. So I would like to ask if I can assign
another 10 x86 VMs to Copr?
I can do it myself, I am just asking in advance if anyone is against it.
I checked the hypervisors and there
Dne 27.6.2017 v 16:17 Kevin Fenzi napsal(a):
>>> - retrace01.qa.fedoraproject.org is almost constantly alerting on swap
>>> being full. Not sure what to do about this, but perhaps we could add
>>> more swap or somehow limit it to use only memory for normal jobs?
>> Few months ago I set postgresql
Dne 17.5.2017 v 15:14 Jeremy Cline napsal(a):
> Hi,
>
> We've moved our documentation to Pagure[0] and turned it into a sphinx
> project. The readme provides guidance on how to contribute, but if you
> run into any trouble just let me know!>
> [0] https://pagure.io/infra-docs/
OK I created PR.
Hi,
I created new SOP for retrace server (see attachemnt). I tried to git-push it,
but got:
$ git push
Counting objects: 6, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 2.02 KiB | 0 bytes/s, done.
Total 6 (delta 3), reused 0
FYI
Přeposlaná zpráva
Předmět: reuse space on retrace02 for retrace01
Datum: Thu, 13 Apr 2017 16:07:37 +0200
Od: Miroslav Suchý <msu...@redhat.com>
Společnost: Red Hat Czech s.r.o.
Komu: abrt-devel-l...@redhat.com
Hi,
for Fedora we have two servers:
ret
Hi,
I am in process in writing playbook for retrace.fedoraproject.org
ABRT team created:
https://github.com/abrt/ansible-role-retrace-server
Which we can use. I just wonder what is best practise for using such 3rd party
roles?
Should I just copy it into our ansible.git? Or should I use
Dne 14.3.2016 v 23:58 Patrick Uiterwijk napsal(a):
> I would suggest you to look at our Request For Resource procedure.
OK. I created:
https://fedorahosted.org/fedora-infrastructure/ticket/5166
> - How well would at least the frontend and package download server work behind
> a load
Dne 12.2.2016 v 22:29 Kevin Fenzi napsal(a):
> But it should migrate sometime... 1.9.x isn't going to be supported all
> that much longer, so it should move to the new 2.0 api as soon as it
> can.
F23 will stay on 1.9.x, isn't it... oh, there is an update filed for F23.
I really hope it did not
Dne 30.1.2016 v 18:40 Kevin Fenzi napsal(a):
> The only other thing related to ansible 2.0 I can think of is that copr
> may need to adjust to the new API if it's using that directly, but it
> can do that on it's own timeframe.
Nope. We are calling ansible python methods directly just on
Dne 25.1.2016 v 18:06 Kevin Fenzi napsal(a):
> Sure, but I was hoping to phase out cloud.fp.o in favor of
> fedorainfracloud.
Hmm. There is a *lot* of people who have .repo file pointing to
copr-be.cloud.fedoraproject.org.
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno,
Dne 25.1.2016 v 16:46 Kevin Fenzi napsal(a):
> I don't think there's anything we can do here.
We can.
We can enable SRS:
http://www.openspf.org/SRS
For postfix there exist:
https://github.com/roehling/postsrsd
Unfortunately not packaged for Fedora.
--
Miroslav Suchy, RHCA
Red Hat, Senior
Dne 22.1.2016 v 22:33 Kevin Fenzi napsal(a):
> fedoraproject.org - Anything with this domain is something that has
> passed though our RFR process and we support fully. This means we
> update status, we alert on them anytime they have issues, we work on
> them anytime they are down, etc.
>
>
Today I sent email to packager-spons...@fedoraproject.org and several email
returned back due SPF protection.
Can someone either implement this:
http://www.openspf.org/Best_Practices/Forwarding
or turn those email aliases to mailing list?
Mirek
Přeposlaná zpráva
Předmět:
Dne 2.12.2015 v 12:14 Pierre-Yves Chibon napsal(a):
> So what do you folks think?
Copr is already migrated to python3 (in upstream) and I'm getting ready to use
python3 on production servers soon.
But Copr (frontend and backend) is using Fedora it is no big deal anyway.
Well we will migrate
Dne 25.9.2015 v 18:47 Kevin Fenzi napsal(a):
> I hope everyone enjoys the nice RHEL7, faster, larger, better batcave.
Hurray!
I especially appreciate the presence of Ansible 1.9, with newer modules (e.g
dnf module).
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp,
Hi,
as you know we have new Fedora Cloud instance.
And we still have the *old* Fedora Cloud instance. I hereby declare fed-cloud02
a.k.a old Fedora Cloud as deprecated.
There is currently 67 machines in running state. And bunch of VM in shutdown
state.
I would kindly ask all owners to:
* not
Dne 6.5.2015 v 21:08 Kevin Fenzi napsal(a):
How about a short term and a longer term plan?
Short term: have copr download and store the src.rpm from build urls.
This would at least make things reproducable and at least someone could
download the src.rpm and send a patch. Along with this a
The log of this classroom:
http://meetbot.fedoraproject.org/fedora-classroom/2015-05-11/fedora-classroom.2015-05-11-15.02.log.html
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
___
infrastructure mailing
On 04/30/2015 01:22 AM, Kevin Fenzi wrote:
How about Fedora Infrastructure Private Servers and we can just call
it FIPS. ;)
Or Fedora Private Cloud - FPC in short :)
/me hides too
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
On 04/30/2015 02:54 AM, Stephen John Smoogen wrote:
So the playbook fails currently because the interfaces ifcfg-br-ex is setup
and restarted before the software for the
type of bridge is installed. I am not sure if you want to fix that and have
me rebuild one more time? Or just go with
the
Long story short:
I declare new Fedora Cloud as final.
There is still lot of work, but that will be always the case. Please use it
(but hold on production things for few days
in case there will be some problem).
I plan to announce Fedora classroom date for those interrested in setup of that
Hi,
Adam Šamalík took dist-git files from fedora-infra ansible.git. He separated
what belongs to dist-git itself and what is
Fedora specific and with cooperation of Dan Mach and Palo Babinčák he created
upstream for dist-git:
https://github.com/release-engineering/dist-git
This is first
On 04/13/2015 03:54 PM, Kevin Fenzi wrote:
Yeah. The one place I thought might be nice was if we wanted to reboot
a compute node to update it, but then I got to thinking, why shouldn't
we also just reboot the instances too and update them as well? ;)
I just tried - when I reboot Compute
On 04/10/2015 06:04 PM, Kevin Fenzi wrote:
I think it might be a good idea to have some swift space setup, but I
am not sure what use cases we fully have for it, so I would say it
should be somewhat small. 100GB or something?
This would also be backed by the equalogics? Or would it be
On 04/02/2015 06:38 PM, Kevin Fenzi wrote:
The new ansible 1.9 version has a known_hosts module. ;)
So, stick at the top of your playbook:
- name: clean out old known_hosts
local_action: known_hosts path=/root/.ssh/known_hosts
name=copr-be-dev.cloud.fedoraproject.org state=absent
Valentin and me are now playing quite a lot with copr-*-dev as part of new
OpenStack testing and I always have to ask
somebody to wipe the entry from known_hosts on lockbox otherwise rbac will
refuse to connect.
Can I suggest to put into ssh_config on lockbox:
Host
On 03/31/2015 10:48 PM, Matthew Miller wrote:
* What is your favorite pro tip for using git?
Sometimes git pull takes long time. Sometimes git start garbage collecting in
situation, where I was under time pressure.
After this line in crontab I have no such problems any more:
40 3 * * * locate
On 03/25/2015 02:40 AM, Kevin Fenzi wrote:
The login here doesn't actually work for me in the new cloud; is it
expected to, or were new passwords allocated?
These were new randomly generated passwords. I can send you that one,
but... see below.
This is kind of tricky.
I have to first set a
On 03/24/2015 11:29 PM, Colin Walters wrote:
- { name: cockpit, email: 'walt...@redhat.com', tenant: scratch,
password: {{cockpit_password}} }
Colin,
to which FAS account this maps? I need to know which SSH key I should upload
for this account. Or you can even provide
me different SSH
I created ./filter_plugins/openstack.py in our ansible.git to easy writing
host_vars in our new cloud.
So instead of ids you can write names of networks, images...
So far I tested it on separate machine and it works, when I have this directory
in ./ and I run ansible playbook in that
directory.
Quick note for those interested in new OpenStack instance:
Routing between two tenants is apparently not possible. Or to be precise
I did not discovered how to do that (and even Larsks did not know).
However ... we can mark same network as shared. This means that those
networks are visible
On 03/12/2015 04:26 PM, Kevin Fenzi wrote:
I think it might be good to have you, me and patrick at least in all
teanants as we often need to look at and diagnose issues other people
have. Of course we could just login as admin, but perhaps we should
discourage that...
Done in commit:
*
The new FedoraCloud (FC) is still not in final state, but if you work with it.
Or you will work with it in future - here
is quick HOWTO regarding certificates.
The cerficate can be found at:
https://fed-cloud09.cloud.fedoraproject.org/pub/fed-cloud09.pem
Your RC file is at:
In new OpenStack instances users belong to this tenants:
- { name: kevin, email: 'ke...@fedoraproject.org', tenant:
infrastructure, password: {{kevin_password}} }
- { name: laxathom, email: 'laxat...@fedoraproject.org', tenant:
infrastructure, password: {{laxathom_password}} }
On 03/07/2015 06:59 PM, Kevin Fenzi wrote:
* We will need to adapt to not giving every instance a floating ip. For
copr, I think this would be fine, as you don't care that they have
*nod* I was not sure how VM behave when does not have public IP so I tested it.
It is basicaly behind NAT and
On 03/09/2015 01:00 PM, Kevin Fenzi wrote:
nova commands worked fine from here, but I didn't really try and do
anything fancy. We could see if the euca stuff will just keep working
for us for now.
It works fine. It is just that if you miss some functionality (and I miss a
lot) and file RFE,
On 03/07/2015 06:59 PM, Kevin Fenzi wrote:
* Can we adjust the default tennat quotas in the playbooks? They seem a
bit low to me given the amount of resources we have.
I put (and tested) the quota for Copr (it is on bottom of playbook).
Can you please write quotas for other tenants (or you
On 03/09/2015 10:29 AM, Miroslav Suchý wrote:
On 03/07/2015 07:29 PM, Kevin Fenzi wrote:
* I see that the tenants have the same internal 172.16.0.0 net right
now, can we make sure we seperate them from each other? ie, I don't
want a infrastructure instance being able to talk to a copr
On 03/07/2015 07:29 PM, Kevin Fenzi wrote:
* I see that the tenants have the same internal 172.16.0.0 net right
now, can we make sure we seperate them from each other? ie, I don't
want a infrastructure instance being able to talk to a copr builder
if we can avoid it.
Are you sure?
On 03/07/2015 06:59 PM, Kevin Fenzi wrote:
All thats set and I can see console in the web dash again just fine for
any of the instances I tried, and they are all https using only.
Works for me too. Nice. Thanks.
I tried to automatize adding of SSH keys using this:
I wonder if we shouldn't
All services are using SSL but novncproxy, which does not worked for me and
according some random notes on internet does
not work over SSL due some bugs.
But novncproxy does not work for me even over plain http. And I do not know
why. If somebody else can check it, it would
be great.
Strange
On 03/06/2015 04:02 PM, Miroslav Suchý wrote:
I tried to automatize adding of SSH keys using this:
TASK: [shell source /root/keystonerc_admin F=$(mktemp) {{ lookup('pipe',
'/srv/web/infra/ansible/scripts/auth-keys-from-fas msuchy') }} $F nova
--os-username msuchy --os-password
On 03/02/2015 10:06 AM, Kashyap Chamarthy wrote:
https://blog-rcritten.rhcloud.com/?p=5 -- Configure Keystone to use
SSL in OpenStack
This great reading. I switched keystone to SSL and it works.
I will try to switch rest of the services.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior
On 03/02/2015 04:00 AM, Kevin Fenzi wrote:
I guess it it only rebooted after
packstack first runs it could work.
That is what I meant. Only needed once, but still nice to have it automated.
* routing between compute nodes and controller using public IP does
not work. Not fatal right now,
Since I'm leaving for one week vacation, I think I may write down current
status of our new OpenStack instance and write
down TODO list. Just in case someone is desperate enough to do some fixes.
I updated docs.git/cloud.txt - mainly which playbooks we use right now and
where to write down IP,
On 02/05/2015 01:13 AM, Kevin Fenzi wrote:
Could we instead call it 'openstack.cloud.fedoraproject.org' or
'controller.cloud.fedoraproject.org' or something? Not sure if that
needs us to rename/reinstall the node, or can just be done in the
cert...
It can be just cname + name in cert.
On 02/05/2015 11:40 AM, Miroslav Suchý wrote:
172.24.0.0 0.0.0.0 255.255.255.0 U 0 00 br-tun
Hmm, I rebooted the machine and this ^^^ line disappeared from route and
172.24.0.100 is now reachable.
I wish I knew what is going on.
--
Miroslav Suchy, RHCE, RHCDS
[root@fed-cloud09 ~(keystone_admin)]# ssh grpadmin@172.24.0.100
ssh: connect to host 172.24.0.100 port 22: No route to host
Nirik can this be result of your (?) change in routes that
[root@fed-cloud09 ~(keystone_admin)]# route -n
Kernel IP routing table
Destination Gateway Genmask
On 02/04/2015 02:32 PM, Kevin Fenzi wrote:
On Tue, 03 Feb 2015 17:54:27 +0100
Miroslav Suchy msu...@redhat.com wrote:
[root@fed-cloud10 etc(keystone_admin)]# telnet 209.132.184.9 443
Trying 209.132.184.9...
telnet: connect to address 209.132.184.9: No route to host
I am able to connect
When I do:
[root@fed-cloud09 ~(keystone_admin)]# cinder type-list
ERROR: Unable to establish connection: [Errno 1] _ssl.c:504: error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Which just transit to:
[root@fed-cloud09 ~(keystone_admin)]# curl -i
On 02/02/2015 04:10 PM, Kevin Fenzi wrote:
Just copy paste the iptables section from base role and adjust the path
to the iptables templates
KISS - I will try this approach. Thanks
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
How do we open ports in ansible today?
I want to open port 5672 for 172.24.0.10/24. Currently it is open only to:
[root@fed-cloud09 ~]# iptables-save |grep 5672
-A INPUT -s 209.132.184.9/32 -p tcp -m multiport --dports 5671,5672 -m comment
--comment 001 amqp incoming
amqp_209.132.184.9 -j
On 01/29/2015 10:50 PM, Mikolaj Izdebski wrote:
What are next steps I need to follow to become apprentice?
As nirik stated, apprentice wiki page is good start.
I would point out
https://infrastructure.fedoraproject.org/infra/docs/sshaccess.txt
as good starting point
Followed by:
On 01/29/2015 05:30 PM, Toshio Kuratomi wrote:
no_log: True
That did the job. Thanks!
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
___
infrastructure mailing list
I have this ansible snippet:
- name: Create users
keystone_user:
login_user=admin login_password={{ ADMIN_PASS }}
login_tenant_name=admin
user={{ item.name }}
email={{ item.email }}
tenant={{ item.tenant }}
password={{ item.password }}
state=present
On 01/08/2015 11:13 PM, Ian Wienand wrote:
Hi,
I'd like to try and find the/a person who could help out with [1].
EPEL version updates are a fairly constant annoyance that causes
issues with CI systems in upstream openstack when the version updates.
As described in the bug, I'd really
Hi,
today I run groups/copr-backend.yml playbook and fedmsg/base notified restart
httpd. Which failed because
httpd is there installed, but not enabled (it is there just as requirement of
webalizer).
So I'm thinking about change (after freeze):
diff --git
Hi,
right now Copr is using stock mock, with its default configuration.
Which means that Copr builders are downloading packages from Fedora mirrors.
I find this sub-optimal, because:
* sometimes is mirror little bit off-sync and occasionally this result in
failed builds.
* while mirrors are
Additionally I would like to do the same for Centos.
Before I ask CentOS guys... do we have somewhere in our datacenter copy of
CentoOS repo?
If not, I'm not sure if I would like to rsync everything. Maybe rather just
setup squid.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software
On 09/17/2014 05:18 PM, Kevin Fenzi wrote:
Yes, ansible makes these anytime a playbook has failed hosts. The idea
is that you can then pass this retry to it on the next run and it will
only run on those hosts that failed.;)
There shouldn't be any in / they should be in/root/
I guess ('cos of
101 - 200 of 239 matches
Mail list logo
