House Of Cards
Patron
- Joined
- May 2, 2017
- Messages
- 211
Good day,
I've been looking around a bit, and can't really find good general information for those of us who update cautiously. With IOCAGE migration officially coming in a couple months, I'm looking toward how to prepare my transition. I'm waiting for the official release of the new GUI, and going to manage my Jails using the interface and officially supported migration scripts before upgrading my WARDEN jails to IOCAGE.
I try to maintain order within my ZFS Pool, and currently have one big pool encompassing all of my storage. I did a test install of a Jail using the beta GUI (11.1-RELEASE), and noticed IOCAGE just makes a mockery of your dataset structure and does what it wants. It creates its "iocage" home right in with your other datasets, and has all sorts of other sub-datasets within it. It's fine that it needs that, but a couple questions/observations come to mind... I'm sure others will be pondering this basic stuff too...
1. Is the default created "iocage" a dataset or ZVOL? Documentation is a little vague in that it says it activates within the current ZPOOL...
2. With WARDEN, you just told it what dataset to use, and it put its stuff in there. I already have a dataset for Jails with things in it. Will we be able to specify the same dataset from the official 11.2 GUI, or is it making its own ZVOL (see question 1)...
3. My current structure is like..
/POOL
/POOL/ZVOL
/POOL/ZVOL/DATASET1
/POOL/ZVOL/DATASET2, etc...
Can I create a ZVOL on the same level as my datasets for the default IOCAGE? Like...
/POOL/ZVOL/IOCAGE_ZVOL/IOCAGE_DATASETS
If I do it that way, will there be any issues sharing my other datasets within IOCAGE Jails, like Plex? From one ZVOL to another?
4. Is there any information about the migration script and how it will function available in advance? I'd like to see what the choices or options will be during the migration...
Perhaps if we can get a clear and concise thread on good practices in advance of the official migration tool, it will prevent a lot of headaches/questions/mistakes for the "non-pros" who do this at home...
Thanks!
I've been looking around a bit, and can't really find good general information for those of us who update cautiously. With IOCAGE migration officially coming in a couple months, I'm looking toward how to prepare my transition. I'm waiting for the official release of the new GUI, and going to manage my Jails using the interface and officially supported migration scripts before upgrading my WARDEN jails to IOCAGE.
I try to maintain order within my ZFS Pool, and currently have one big pool encompassing all of my storage. I did a test install of a Jail using the beta GUI (11.1-RELEASE), and noticed IOCAGE just makes a mockery of your dataset structure and does what it wants. It creates its "iocage" home right in with your other datasets, and has all sorts of other sub-datasets within it. It's fine that it needs that, but a couple questions/observations come to mind... I'm sure others will be pondering this basic stuff too...
1. Is the default created "iocage" a dataset or ZVOL? Documentation is a little vague in that it says it activates within the current ZPOOL...
2. With WARDEN, you just told it what dataset to use, and it put its stuff in there. I already have a dataset for Jails with things in it. Will we be able to specify the same dataset from the official 11.2 GUI, or is it making its own ZVOL (see question 1)...
3. My current structure is like..
/POOL
/POOL/ZVOL
/POOL/ZVOL/DATASET1
/POOL/ZVOL/DATASET2, etc...
Can I create a ZVOL on the same level as my datasets for the default IOCAGE? Like...
/POOL/ZVOL/IOCAGE_ZVOL/IOCAGE_DATASETS
If I do it that way, will there be any issues sharing my other datasets within IOCAGE Jails, like Plex? From one ZVOL to another?
4. Is there any information about the migration script and how it will function available in advance? I'd like to see what the choices or options will be during the migration...
Perhaps if we can get a clear and concise thread on good practices in advance of the official migration tool, it will prevent a lot of headaches/questions/mistakes for the "non-pros" who do this at home...
Thanks!