Confluence Server Log 2017 on Azure
- 1 Next Update
- 1.1 Operations
- 2 Plugins
- 3 November 24, 2017 - Renew of Online License Key, Tin
- 4 September 15, 2017 - Updates and Server Reboot, Roderick
- 5 August 4, 2017 - Server Rebooted, Roderick
- 6 July 21, 2017 - Updates and Rebooted Server, Roderick
- 7 June 2, 2017 - Installed Redaction to Secure Specific Content, Tin
- 8 May 26, 2017 - Disabling Automatic Security Updates, Roderick
- 9 May 5, 2017 - Added Offsite Backups for Confluence, Roderick
- 10 April 12, 2017 - Disabling Automatic Updates, Roderick
- 11 March 26, 2017 - Hardened Apache, Roderick
- 12 February 23, 2017 - Added Analytics, Roderick
- 13 February 22, 2017
- 14 Feb 22, 2017 - Made Bonsai Framework Searchable on the Internet, Tin
- 15 February 08, 2017 - Resized Confluence Server, Roderick
- 16 January 24, 2017 - LXD, Tin, Roderick
- 17 January 17, 2017 - Server Configuration, Tin, Roderick
Next Update
What are we doing next.
Operations
Plugins
November 24, 2017 - Renew of Online License Key, Tin
Product License renewal. Must use Tin's personal gmail account to log into My Atlassian,
Direct link provided through Confluence reminder.
After new licence keys issues, copy into Confluence.
License now expires, Dec 27, 2018
September 15, 2017 - Updates and Server Reboot, Roderick
Bonsai went down due to stuck thread
Applied server updates (for what?) and rebooted the server
August 4, 2017 - Server Rebooted, Roderick
Bonsai went down from a host reboot, had to reboot the server to clear the hung threads
July 21, 2017 - Updates and Rebooted Server, Roderick
System update and reboot
June 2, 2017 - Installed Redaction to Secure Specific Content, Tin
Updated all plugins to current.
Installed Redaction ... looks promising to secure specific content
May 26, 2017 - Disabling Automatic Security Updates, Roderick
Disabled Automatic Security Updates located in 20auto-upgrades
May 5, 2017 - Added Offsite Backups for Confluence, Roderick
Added Automated backups moved to Offsite
April 12, 2017 - Disabling Automatic Updates, Roderick
Disabled Automatic Updates in file 10periodic
March 26, 2017 - Hardened Apache, Roderick
Secured Apache
February 23, 2017 - Added Analytics, Roderick
Added Google Analytics
February 22, 2017
Resized the zpool to 20GB because containers were throwing out of space errors
Turned off robots.txt (prevents Search Engines from calling)
Submitted www.bonsaiframework.com to Google Search Engine (Search Console)
Added Balsamiq plug-in through Confluence web console
Feb 22, 2017 - Made Bonsai Framework Searchable on the Internet, Tin
Now that we are stable with a much larger server, we can make the Bonsai Framework searchable on the Internet. We'll start with Google, but should include the other top engines,
10:00pm - Turned off robots.txt (which prevents Search Engines from calling)
10:03pm - Submitted www.bonsaiframework.com to Google Search Engine (Search Console) while logged in as tin.pham@gmail.com (not sure if logging in matters)
Added Balsamiq plug-in through Confluence web console (free for non-profits) and submitted tin.pham@gmail profile linked to Confluence
February 08, 2017 - Resized Confluence Server, Roderick
Server was resized to fit confluence $51.56/month
Memory increased to 3.5GB
Virtual Server = bonsaifw02host
Built using 16.04 LTS
Fully migrated and www.bonsaiframework.com is now live
Next steps Working on backup solution
January 24, 2017 - LXD, Tin, Roderick
We created first iteration straight migration VMs.
Resource Group = bfgroup
Virtual Server = bonsaifw01host
Built using Ubuntu 16.10 (we'll switch back to LTS for iteration 2)
3 LXD Tiers created (all using LXD dynamic IPs)
NAT setup for port 80 host to web server
Azure Native Firewall (NSG) port 80 Configured
Confluence Installed and ready for first run to migrate the data.
January 17, 2017 - Server Configuration, Tin, Roderick
Roderick gave Tin access
Tin created virtual machine using Ubuntu 16.04 LTS per research with setupadmin
Roderick logged in added fail2ban and then rest of BonsaiFramework Setup
Installed LXD with following,
Name of the storage backend to use (dir or zfs) [default=zfs]:
Create a new ZFS pool (yes/no) [default=yes]?
Name of the new ZFS pool [default=lxd]:
Would you like to use an existing block device (yes/no) [default=no]?
Size in GB of the new loop device (1GB minimum) [default=15]:
Would you like LXD to be available over the network (yes/no) [default=no]?
Would you like stale cached images to be updated automatically (yes/no) [default=yes]?
Would you like to create a new network bridge (yes/no) [default=yes]?
What should the new bridge be called [default=lxdbr0]?
What IPv4 subnet should be used (CIDR notation, "auto" or "none") [default=auto]?
What IPv6 subnet should be used (CIDR notation, "auto" or "none") [default=auto]?
LXD has been successfully configured.