> About of the translation:
> - What do these things?:
> - Are these options for the user, or messages?
> - Please explain clearly, and if are messages, please also put the full
> message for
> do the best translation
Thos are options:
>
> #: ../www/manager/openvz/Network.js:88
> #, fuzzy
> msgi
I have a answers:
About of the translation:
- What do these things?:
- Are these options for the user, or messages?
- Please explain clearly, and if are messages, please also put the full
message for do the best translation
#: ../www/manager/openvz/Network.js:88
#, fuzzy
msgid "Host device name"
> Dietmar> I think your setup makes no sense.
>
> I respect your opinion. Please respect mine.
>
> All I asked for in the beginning was a one-line patch to allow a different
> configuration in proxmox, that is useful to "me" and does not hurt "you".
This hurts me, because I have to test that cod
Hi all,
I don't know whether you all are aware of mininet for testing open
vswitch and open flow?
http://mininet.org/
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir datanom net
http://pgp.mi
>>but that only works if the optimize flag is set (else we do not have that
>>rule)?
I wanted to say something like:
ruleset_insertrule($ruleset, "PVEFW-FORWARD", "-m conntrack --ctstate
INVALID,NEW -j PVEFW-smurfs") if $hostfw_options->{nosmurfs};
ruleset_insertrule($ruleset, "PVEFW-F
Martin>If someone wants a custom Ceph setup with experimental
features, then default Proxmox VE Ceph GUI is probably not the right
tool for this.
I agree. This is why I don't want to patch the gui. I need a low-level
door for doing "advanced" stuff, if block devices can be considered
advanced (md/
> However, if the decision was made that proxmox "gui" will only use disks
> because of "simplicity", then I see nothing wrong with doing some advanced
> tasks on the console, provided they don't break the GUI or misbehave in other
> ways.
I think your setup makes no sense.
__
Hello Paul,
The basic idea of Proxmox VE Ceph Server and GUI is a well-defined setup with a
clearly defined feature set. Easy to setup, easy to maintain and easy to
support.
So adding anything which is against this goal makes no sense here. As soon as
Ceph firefly is stable, we will do tests a
2014-04-18 10:24 GMT+02:00 Dietmar Maurer :
>> Dietmar wrote:
>> >>>If you want to manage OSDs on ZFS, please also provide patches to
>> >>>make the GUI able to manage that.
>>
>> The gui actually works quite nicely, once the OSD is added by hand with
>> pveceph
>> createosd.
>
> So the most impor
> just put the rule in PVEFW-FORWARD, after
>
> -A PVEFW-FORWARD -m conntrack --ctstate INVALID -j DROP -A PVEFW-
> FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
but that only works if the optimize flag is set (else we do not have that rule)?
__
> Dietmar wrote:
> >>>If you want to manage OSDs on ZFS, please also provide patches to
> >>>make the GUI able to manage that.
>
> The gui actually works quite nicely, once the OSD is added by hand with
> pveceph
> createosd.
So the most important function will not work on the GUI.
__
> I interpret it in a positive way: The ceph developers are aware of ZFS and
> they
> recognize that there could be some usefulness in using it under ceph.
My understanding is that they will and use a faster approach like leveldb in
future.
___
pve-d
I mean, I we have a bad packet (smurf or bad tcpflags) attack,
for each packet it need to go to the whole chains (vmbrxxx,tapxxx,..) to match
the nosmurf or tcpflag block rule.
just put the rule in PVEFW-FORWARD, after
-A PVEFW-FORWARD -m conntrack --ctstate INVALID -j DROP
-A PVEFW-FORWARD -m
Dietmar wrote:
>>>If you want to manage OSDs on ZFS, please also provide patches to make the
>>>GUI
>>>able to manage that.
The gui actually works quite nicely, once the OSD is added by hand
with pveceph createosd. You can in/out and stop/start the osd as you
do with all other osd. A ZVol emulate
> Yes, I think it's ok. It could also improve performance, for bad packets, less
> lookups in vmbr, tap chains.
oh, how can we improve performance?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-
15 matches
Mail list logo
