It's not possible in version 5.x, but version 6 can do it with a few tweaks. David Loper at ClearCenter is the team lead on this type of implementation and I know he's working on at least one large deployment at the moment. ClearCenter has custom import tools, custom configurations and the knowledge set for this type of deployment.
From my developer perspective, I run tests with 100,000 users from time to time so I can see how well webconfig behaves in this type of scenario.
- LDAP authentification (delay,...) - shouldn't be a problem, tuning required
-User management interface in webconfig - the page load will be big (2 MB?), but search/filter functions are all client side and fast.
- Certificate Authority - I don't suspect any issues here
- User's change password - I don't suspect any issues here
- User's Certificate download (delay) - this is now done on demand instead of when the user is created, so no problems in version 6
Just an FYI. The "Security Certificates" for OpenVPN pose a bit of a challenge in master/slave mode. That's what's holding it back right now (the OpenVPN server itself is pretty much ready to go).
Good point Tim! Sorry about the Flexshare confusion in Marketplace. Assuming I don't get distracted by the usual whirlwind, I can push the Flexshare app out to the build system shortly.
Dont suppose theres a 5.2 to 6.xx upgrade out there?
Nope. The upgrade path will likely be available in a later version. The upstream vendor doesn't officially support upgrades, but we'll at least have an unofficial way to go about it. About half of the apps in 6 already have upgrade scripts in place, but nothing has been fully tested yet.
I added Tim's miniupnpd package to the build system and the RPM is ready for testing. To install and run it:
Code:
yum --enablerepo=clearos-test install miniupnpd
service miniupnpd start
I think that's it. Please report back here on how things are working.
For hackers
I bumped the version to the latest one available. The rest is all Tim's work.
For those of you who plan on diving into the build system, you will need to upgrade the clearos-devel package to get the "mockbuild" step working (as described in one of the packaging docs). You will also need to install the iptables-devel dependency if you want to build the RPM on your system:
For Tim and any others who would like to make changes, you can add patches, as well as update the config and init scripts in CVS. When you are ready to push it to the build system, just let me know. The documentation on the process is here, but it might need a few updates.
The first version of the Active Directory Connector is available, but I would wait for the updated version that is coming out shortly (with the release of ClearOS Professional Beta 3). If you send a quick note to me (pbaldwin@clearcenter.com) with your ClearCenter account name, I'll make sure there's an evaluation subscription added to your account -- I'm not sure the self-serve evaluation will be available in Beta 3.
In theory, the RADIUS app in version 6 should behave the exact same way. The version 5 release was converted over to the way things are done in 6, but the app has not been verified.
I'll work with Darryl to get the latest source code out late this week. One of the goals is to provide a template/demo on what needs to get done on both ClearOS and Android. Copy, paste, run with it! I'll keep you posted.
We're stumped on this one. We have looked through the logs and stats and the servers look fine. We haven't changed anything with our mirrors in the last couple of years (though we are rolling out new infrastructure right now), so we're looking for other potential causes:
- An issue with our data center (note: the two reported IPs come out of two different data centers, but the same provider - SoftLayer)
- A web browser change
- Other
If you don't mind me asking... what web browser are you using (if you were using a browser)? What version?
James Joseph wrote: * Beta 3 was suppose to include flexshares I see it on the market place but while downloading I'm getting an error I'm guessing this isn't available yet ?
Not there yet... it's coming!
The radius that's in ClearOS is that only as a connector or will it be possible to use RADIUS as your authenticator to make users and groups ?
I don't know RADIUS at all. I was involved with the implementation, but I have no idea how that implementation is supposed to work. If you send a PM to David Loper, he might be able to provide some guidance (preferably in the forums instead of in private though). As it stands today, RADIUS will not be appearing in Marketplace in the final release. We'll keep it installable via yum, but right now I don't even know if it works
I don't see in the user section where you can add services per user like in 5.2 i.e. give them access to windows networking/mailbox. Is it not possible to do this anymore or is this feature not in yet?
The options are still there, but the Windows Networking option is hidden (for now). All other options (PPTP, Web Proxy) are there under "App Policies" when creating/editing a user. There's even a new "Shell Extension" available in Marketplace if you want to enable shell access for users (geeks only!). For Windows Networking, there's some debate on how much information to expose, notably:
For those running a simple file server, those last 3 fields are not relevant (confusing and just clutter). For now, we'll probably just go with "Account Status" and leave the rest hidden.
Oh... the Horde/Kolab mail system will be available in the 6.3 release (which is when we plan on supporting 5.x upgrades in some kind of way). Zarafa and Google Apps are going to be the "default" mail systems in version 6. I don't know if "default" is the right word here since we're leaving it up to end users. The "install wizard" will probably step folks through this step, i.e.
Pick a Messaging/Groupware Solution
- Google Apps
- Zarafa Standard / Zarafa Community
- Horde/Kolab
I imported the package into the build system and did a successful test build. I need to ping Tim and Shad about a couple of open topics and we should then be able to roll with a build. More to come!
Tim Burgess wrote: Had to remove clearos-devel, glibc-devel and glibc-headers from clearcore-current before it would let me upgrade from beta2
Upgrading a developer environment is always a bit trickier! I just did that today and had to purge some cruft. It should be less of a hassle as time goes on.
Also is the version of this RPM correct? clearos-logos-community-60.0.14-2.v6.1.noarch.rpm ...60 seems a little high, perhaps 6.0?
That's just the upstream version number - definitely an odd one though.
