when adding LVM Storage, do not overwrite user input for content
and if Storage and Container is selected
show the proper names
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the usual:
* move static conf. to class definition
* change "show" event to "activate"
special attention here to the bufferedRenderer: false value here:
if the grid panel has bufferedRenderer: true (default) and the
store is our Diffstore, it adds the Summary Row twice, once before
the store is loaded and once after.
because there probably will not be many pools in a ceph configuration
managed by the gui, we can safely deactivate bufferedRenderer
(according to extjs documentation, this is intended for gridpanels
with several thousand rows, which is not an issue with ceph pools
i think)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
* moved static configuration to class definition
* changed the width of the headers (because most were too small)
* changed "show" event to "activate"
special attention for the data fields:
changed the id from type integer to default type, because
extjs cannot convert form integer for this field
(if we do not do this, the whole ceph tab breaks)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this fixed the ceph subtabs: Status,Config,Crush,Disks,Monitor
with the usual fixes:
* moving static configuration to class definition
* change deprecated fields
* make xtypes consistent
* change "show" event to "activated"
special note: i moved the subtabs to the left (like the firewall),
because the alternatives are really bad (top looks not good, bottom
is not obvious)
i also changed the width of some headers in gridpanels when the
title was too long
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
some extjs components expect the datachanged event
to be fired, we changed this to refresh (which
worked for most things, but not all),
this patch fires both events when data is loaded
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the grouped headers in gridpanels use space like
there is no tomorrow, this patch makes it a little
denser
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Not all document default values matched their actual
default, fix this by not maintaining two separate lists of
default values.
Note that this changes:
- the default compression from none to the documented LZO
- the documented default mode from stop to snapshot
our parent class Ext.grid.GridPanel sets 'tbar: null'
and Ext.applyIf() will only apply our property
if it is undefined, so switch to Ext.apply()
it is safe to use Ext.apply() because none of these classes is further extended,
so we don't have to worry that might me might override a toolbar
set further down by a child class
this fixes allows the panel to display its top toolbar with add/edit buttons
we used a custom 'data' property to pass around the items to
add to the store, but this property is now used by ExtJS to
store content for the component template
also move to declarative style, saves lines
if one selected an item in a ComboGrid which was already selected,
the ComboGrid would not close (as expected), this patch fixes this
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
The exclude list is built from both the command line
parameters and the config. If no excludes are passed on the
command line we previously copied the defaults to it,
effectively passing them twice.
Call split_args() on the 'exclude-path' option read from
/etc/vzdump.conf
With the move to the generic JSONSchema::parse_config() in
commit cc61ea36 the call to split_args() for 'exclude-path'
was dropped breaking the 'exclude-path' option.
The schema's documentation was already updated to reflect
the change from regular expressions to shell globs, but the
pod entry in CLI/vzdump.pm wasn't.
Also C<> is not interpreted in verbatim (space-prefixed)
lines so it showed up as literal text.
