Sure! Sounds good!
Chris
Sent from my iPhone
> On Oct 24, 2017, at 3:57 PM, Belmiro Moreira
> wrote:
>
> Hi,
> can we add this meeting into the official IRC meetings page?
> https://wiki.openstack.org/wiki/Meetings
> http://eavesdrop.openstack.org/
>
>
Similarly, if you have the capability in your compute gear you could do
SR-IOV and push the problem entirely into the instance (but then you miss
out on Neutron secgroups and have to rely entirely on in-instance
firewalls).
Cheers,
On 25 October 2017 at 01:41, Jeremy Stanley
Hi everyone,
Don't forget tomorrows meeting for the PublicCloudWorkingGroup.
November 25th 1400 UTC in IRC channel
#openstack-meeting-3
Etherpad and agenda: https://etherpad.openstack.org/p/publiccloud-wg
Regards,
Tobias Rydberg
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
can we add this meeting into the official IRC meetings page?
https://wiki.openstack.org/wiki/Meetings
http://eavesdrop.openstack.org/
thanks,
Belmiro
On Tue, 24 Oct 2017 at 15:51, Chris Morgan wrote:
> Next meeting in about 10 minutes from now
>
> Chris
>
> --
>
Meeting minutes here:
Meeting ended Tue Oct 24 15:00:00 2017 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
11:00 AM Minutes:
http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-24-14.00.html
11:00 AM Minutes (text):
Oh hey there Curtis!
> Basically I expect there is no dhcp service. Double check the network has
dhcp?
There's DHCP running on the net nodes, but the dhcp logs don't show any
errors or warnings
In the DHCP logs, the only difference I can see is when booting from
provider it says its building
Folks,
Per our meeting discussion on 10/16:
http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-10-16-18.03.log.html#l-100
We will start having UC IRC meetings in two different times and we need to move
our meeting from the #openstack-meeting channel to #openstack-uc
This is the commit for
On 2017-10-24 20:18:30 +0900 (+0900), Jean-Philippe Méthot wrote:
> We’ve just recently been hit on by a low-level DDoS on one of our
> compute nodes. The attack was fulling our conntrack table while
> having no noticeable impact on our server load, which is why it
> took us a while to detect it.
Next meeting in about 10 minutes from now
Chris
--
Chris Morgan
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Hi all,
We’ve just recently been hit on by a low-level DDoS on one of our compute
nodes. The attack was fulling our conntrack table while having no noticeable
impact on our server load, which is why it took us a while to detect it. Is
there any recommended practice regarding server
Hello Gordon,
I had tried to configure my pipeline so it would also gather information from
ODL since i was trying to get as much information as possible. I commented out
everything related to ODL and the errors stopped. Any ideas about the cause of
this behavior? I am attaching :
- My
11 matches
Mail list logo